From cdea8ff278ef80f2ea234c78d176bf90fdb9dfd0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:00:52 +0900 Subject: [PATCH 0001/1932] New translations yaml-validation.yml (Romanian) --- ro/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 ro/yaml-validation.yml diff --git a/ro/yaml-validation.yml b/ro/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/ro/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From f28e9717c3596ac6bf7b515672781a54526648cc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:00:52 +0900 Subject: [PATCH 0002/1932] New translations accounts.yml (Danish) --- da/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 da/accounts.yml diff --git a/da/accounts.yml b/da/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/da/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From f4313b085c1807c597aea19a8af97ecd2c189d54 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:00:53 +0900 Subject: [PATCH 0003/1932] New translations yaml-validation.yml (Vietnamese) --- vi/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 vi/yaml-validation.yml diff --git a/vi/yaml-validation.yml b/vi/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/vi/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 8cefd43fcf396aa670d8fe38f0f9aeef39d0410d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:00:54 +0900 Subject: [PATCH 0004/1932] New translations yaml-validation.yml (Portuguese, Brazilian) --- pt/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 pt/yaml-validation.yml diff --git a/pt/yaml-validation.yml b/pt/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/pt/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 5625442a8a75f2d858aac459d789c19c881f2ffb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:00:55 +0900 Subject: [PATCH 0005/1932] New translations accounts.yml (Romanian) --- ro/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 ro/accounts.yml diff --git a/ro/accounts.yml b/ro/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/ro/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 9573f9a85a928f71d64740bb76e296b5040a5625 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:00:56 +0900 Subject: [PATCH 0006/1932] New translations accounts.yml (French) --- fr/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 fr/accounts.yml diff --git a/fr/accounts.yml b/fr/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/fr/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 678103b756d9531c5e3ca2c4398603bf6f9415c2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:00:57 +0900 Subject: [PATCH 0007/1932] New translations accounts.yml (Spanish) --- es/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 es/accounts.yml diff --git a/es/accounts.yml b/es/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/es/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From c286ac3b7331b5052bd0679b1f110e858e169c2d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:00:58 +0900 Subject: [PATCH 0008/1932] New translations accounts.yml (Afrikaans) --- af/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 af/accounts.yml diff --git a/af/accounts.yml b/af/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/af/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 5d8b15759eaf9e58ce1e2f1e06b77c5af3c597b4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:00:59 +0900 Subject: [PATCH 0009/1932] New translations accounts.yml (Arabic) --- ar/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 ar/accounts.yml diff --git a/ar/accounts.yml b/ar/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/ar/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From ce85b2ce2ba6b6a6fe0399832d40e73732ebec99 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:01 +0900 Subject: [PATCH 0010/1932] New translations accounts.yml (Catalan) --- ca/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 ca/accounts.yml diff --git a/ca/accounts.yml b/ca/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/ca/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 1cc0acb3588cc1b1382533e4930f58ab38d8e942 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:02 +0900 Subject: [PATCH 0011/1932] New translations accounts.yml (Czech) --- cs/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 cs/accounts.yml diff --git a/cs/accounts.yml b/cs/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/cs/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 3ba46f01d57e79ecd55e72e92a72b1ee3111947a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:03 +0900 Subject: [PATCH 0012/1932] New translations accounts.yml (German) --- de/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 de/accounts.yml diff --git a/de/accounts.yml b/de/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/de/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 6bfcc9f4d9c197c62dedf80aaf1afb67151b5ed0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:04 +0900 Subject: [PATCH 0013/1932] New translations yaml-validation.yml (Chinese Traditional) --- zh/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 zh/yaml-validation.yml diff --git a/zh/yaml-validation.yml b/zh/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/zh/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From d861abe98f293e17c5a3d670b90db7b3bfb0b44b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:05 +0900 Subject: [PATCH 0014/1932] New translations accounts.yml (Greek) --- el/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 el/accounts.yml diff --git a/el/accounts.yml b/el/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/el/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 090871a44e772cc09bdfd8b675dd62a1b1c9f3ac Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:06 +0900 Subject: [PATCH 0015/1932] New translations accounts.yml (Finnish) --- fi/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 fi/accounts.yml diff --git a/fi/accounts.yml b/fi/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/fi/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 1252f3014ebe0e2fff683c6ea5011169355c7eb3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:07 +0900 Subject: [PATCH 0016/1932] New translations accounts.yml (Hebrew) --- he/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 he/accounts.yml diff --git a/he/accounts.yml b/he/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/he/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 21059428901b4ec516283206d6b1c80ecea0a36a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:08 +0900 Subject: [PATCH 0017/1932] New translations accounts.yml (Hungarian) --- hu/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 hu/accounts.yml diff --git a/hu/accounts.yml b/hu/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/hu/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 837d612c6a9eaa94d92190b3ace0d52672c0102d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:09 +0900 Subject: [PATCH 0018/1932] New translations accounts.yml (Italian) --- it/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 it/accounts.yml diff --git a/it/accounts.yml b/it/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/it/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 5954557d3298f2b007be8bc99dfcbb63df6c2d14 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:10 +0900 Subject: [PATCH 0019/1932] New translations accounts.yml (Japanese) --- ja/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 ja/accounts.yml diff --git a/ja/accounts.yml b/ja/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/ja/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From da605f87f52f0a115e2e53c4cf2c5c15cdfc28ab Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:11 +0900 Subject: [PATCH 0020/1932] New translations accounts.yml (Korean) --- ko/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 ko/accounts.yml diff --git a/ko/accounts.yml b/ko/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/ko/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 2051435d890be333703da36d675a28c6c0f09500 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:11 +0900 Subject: [PATCH 0021/1932] New translations accounts.yml (Dutch) --- nl/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 nl/accounts.yml diff --git a/nl/accounts.yml b/nl/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/nl/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 4f3001f790cf426177ff6ec62544ab2025758fcc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:13 +0900 Subject: [PATCH 0022/1932] New translations accounts.yml (Norwegian) --- no/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 no/accounts.yml diff --git a/no/accounts.yml b/no/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/no/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From ba63d9aeb0525c1dd0eaaa2b1554b3bd16397bca Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:13 +0900 Subject: [PATCH 0023/1932] New translations accounts.yml (Polish) --- pl/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 pl/accounts.yml diff --git a/pl/accounts.yml b/pl/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/pl/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 3ece3bc06442272a0493e475eb3053e6f19793bd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:14 +0900 Subject: [PATCH 0024/1932] New translations yaml-validation.yml (English) --- en/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 en/yaml-validation.yml diff --git a/en/yaml-validation.yml b/en/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/en/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 79999057f81b24ef0bb6d2a95a343d265be3df7a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:16 +0900 Subject: [PATCH 0025/1932] New translations yaml-validation.yml (French) --- fr/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 fr/yaml-validation.yml diff --git a/fr/yaml-validation.yml b/fr/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/fr/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 35eb27c4eb58bf261156592bb74f1bb2055c1c48 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:17 +0900 Subject: [PATCH 0026/1932] New translations yaml-validation.yml (Hungarian) --- hu/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 hu/yaml-validation.yml diff --git a/hu/yaml-validation.yml b/hu/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/hu/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From d4de257cf8b7aa262237b25ccca8c978f70126f9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:18 +0900 Subject: [PATCH 0027/1932] New translations yaml-validation.yml (Spanish) --- es/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 es/yaml-validation.yml diff --git a/es/yaml-validation.yml b/es/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/es/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From f73129f7af82f63e3848d4c40f5ab2c5de74b133 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:19 +0900 Subject: [PATCH 0028/1932] New translations yaml-validation.yml (Afrikaans) --- af/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 af/yaml-validation.yml diff --git a/af/yaml-validation.yml b/af/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/af/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 65a9b74b81be95be1aa8a1d8926d53d812dd6939 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:20 +0900 Subject: [PATCH 0029/1932] New translations yaml-validation.yml (Arabic) --- ar/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 ar/yaml-validation.yml diff --git a/ar/yaml-validation.yml b/ar/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/ar/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 64f4974c8dcd14da2655b683720a14760bb132d4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:20 +0900 Subject: [PATCH 0030/1932] New translations yaml-validation.yml (Catalan) --- ca/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 ca/yaml-validation.yml diff --git a/ca/yaml-validation.yml b/ca/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/ca/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 21e2444aabc1717ff9ffb97df2a219de0093ed05 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:21 +0900 Subject: [PATCH 0031/1932] New translations yaml-validation.yml (Czech) --- cs/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 cs/yaml-validation.yml diff --git a/cs/yaml-validation.yml b/cs/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/cs/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 0ebf9dd69c2e7f9e19a78d7873e586059435bcdd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:22 +0900 Subject: [PATCH 0032/1932] New translations yaml-validation.yml (Danish) --- da/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 da/yaml-validation.yml diff --git a/da/yaml-validation.yml b/da/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/da/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 8c47a5ad82e38b546e7e177a67b937f2a3daf20f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:23 +0900 Subject: [PATCH 0033/1932] New translations yaml-validation.yml (German) --- de/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 de/yaml-validation.yml diff --git a/de/yaml-validation.yml b/de/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/de/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 11de004c28a5ffd908a8b2acf1387b101827d049 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:24 +0900 Subject: [PATCH 0034/1932] New translations yaml-validation.yml (Greek) --- el/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 el/yaml-validation.yml diff --git a/el/yaml-validation.yml b/el/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/el/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From cbe37fa3022769de3746440740c7f81ba4eb72cd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:25 +0900 Subject: [PATCH 0035/1932] New translations yaml-validation.yml (Finnish) --- fi/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 fi/yaml-validation.yml diff --git a/fi/yaml-validation.yml b/fi/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/fi/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 67ca0453aef16034e3373e83e3f34e8cabe465be Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:26 +0900 Subject: [PATCH 0036/1932] New translations yaml-validation.yml (Hebrew) --- he/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 he/yaml-validation.yml diff --git a/he/yaml-validation.yml b/he/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/he/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From cbace8d6f8db3a5188df3230ed8bc1550591b156 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:27 +0900 Subject: [PATCH 0037/1932] New translations yaml-validation.yml (Italian) --- it/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 it/yaml-validation.yml diff --git a/it/yaml-validation.yml b/it/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/it/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 22fa5b76cccef9d9294b71e99473bdd56a885a06 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:28 +0900 Subject: [PATCH 0038/1932] New translations yaml-validation.yml (Ukrainian) --- uk/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 uk/yaml-validation.yml diff --git a/uk/yaml-validation.yml b/uk/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/uk/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 3bfb843a99f0ee81e9e412ec87ef05b1285323ab Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:28 +0900 Subject: [PATCH 0039/1932] New translations yaml-validation.yml (Japanese) --- ja/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 ja/yaml-validation.yml diff --git a/ja/yaml-validation.yml b/ja/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/ja/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 64849e0b5eb640c2062d9c3c15f220e458b467a0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:29 +0900 Subject: [PATCH 0040/1932] New translations yaml-validation.yml (Korean) --- ko/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 ko/yaml-validation.yml diff --git a/ko/yaml-validation.yml b/ko/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/ko/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 41e7b53c55a00608d8394e42caff38db4d734ef3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:30 +0900 Subject: [PATCH 0041/1932] New translations yaml-validation.yml (Dutch) --- nl/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 nl/yaml-validation.yml diff --git a/nl/yaml-validation.yml b/nl/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/nl/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From f0eaf5b3d9e1e986dc40191d6fcad20523e3249c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:31 +0900 Subject: [PATCH 0042/1932] New translations yaml-validation.yml (Norwegian) --- no/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 no/yaml-validation.yml diff --git a/no/yaml-validation.yml b/no/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/no/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 96a23ecd196a260b28fc712f5edf6ffd68d29062 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:32 +0900 Subject: [PATCH 0043/1932] New translations yaml-validation.yml (Polish) --- pl/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 pl/yaml-validation.yml diff --git a/pl/yaml-validation.yml b/pl/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/pl/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 36e5d22a222e6836b39bb8b33c524fba83dddc56 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:34 +0900 Subject: [PATCH 0044/1932] New translations yaml-validation.yml (Russian) --- ru/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 ru/yaml-validation.yml diff --git a/ru/yaml-validation.yml b/ru/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/ru/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 4134166ebebf4f0c3b7bdf3cfd1192b9dbf726e8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:34 +0900 Subject: [PATCH 0045/1932] New translations yaml-validation.yml (Serbian (Cyrillic)) --- sr/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 sr/yaml-validation.yml diff --git a/sr/yaml-validation.yml b/sr/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/sr/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 82ee123321c372323d357a95704187bdcccad36b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:35 +0900 Subject: [PATCH 0046/1932] New translations yaml-validation.yml (Swedish) --- sv/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 sv/yaml-validation.yml diff --git a/sv/yaml-validation.yml b/sv/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/sv/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 69247cb21397632d35d842fe230781a54f91637b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:36 +0900 Subject: [PATCH 0047/1932] New translations yaml-validation.yml (Turkish) --- tr/yaml-validation.yml | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 tr/yaml-validation.yml diff --git a/tr/yaml-validation.yml b/tr/yaml-validation.yml new file mode 100644 index 00000000000..3b976ad39ae --- /dev/null +++ b/tr/yaml-validation.yml @@ -0,0 +1,37 @@ +--- +#This is a basic workflow to help you get started with Actions +name: CI +#Controls when the workflow will run +on: + #Triggers the workflow on push or pull request events but only for the main branch + push: + branches: + - main + pull_request: + branches: + - main + #Allows you to run this workflow manually from the Actions tab + workflow_dispatch: +#A workflow run is made up of one or more jobs that can run sequentially or in parallel +jobs: + #This workflow contains a single job called "validate-yaml" + validate-yaml: + #The type of runner that the job will run on + runs-on: ubuntu-latest + #Steps represent a sequence of tasks that will be executed as part of the job + steps: + - + uses: actions/checkout@v2 + - + name: YAML Lint + uses: ibiqlik/action-yamllint@v3.0.4 + with: + config_data: | + extends: default + rules: + line-length: disable + new-line-at-end-of-file: disable + trailing-spaces: disable + document-start: disable + empty-lines: disable + truthy: disable From 6a178da51a926000b4e9011abb5093bd6399ad8c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:37 +0900 Subject: [PATCH 0048/1932] New translations accounts.yml (Portuguese) --- pt/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 pt/accounts.yml diff --git a/pt/accounts.yml b/pt/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/pt/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 11e10767ccbe77394f7f477bc3b18ef570c7a4c5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:38 +0900 Subject: [PATCH 0049/1932] New translations accounts.yml (Russian) --- ru/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 ru/accounts.yml diff --git a/ru/accounts.yml b/ru/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/ru/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 93dbe869e3536dd7c6f622d2936d35f0fff67718 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:39 +0900 Subject: [PATCH 0050/1932] New translations common.yml (Swedish) --- sv/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 sv/common.yml diff --git a/sv/common.yml b/sv/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/sv/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 33ffc4e8a1132a35ff1d75db1f0cf370f024788c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:40 +0900 Subject: [PATCH 0051/1932] New translations common.yml (Japanese) --- ja/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 ja/common.yml diff --git a/ja/common.yml b/ja/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/ja/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 0e50d91f31f80bee491e6612388ccc913532668d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:41 +0900 Subject: [PATCH 0052/1932] New translations accounts.yml (Serbian (Cyrillic)) --- sr/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 sr/accounts.yml diff --git a/sr/accounts.yml b/sr/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/sr/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From d2c0974d34ff8059311e7e3c7e89516cbcfc44a4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:42 +0900 Subject: [PATCH 0053/1932] New translations common.yml (Dutch) --- nl/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 nl/common.yml diff --git a/nl/common.yml b/nl/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/nl/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From f79b634b44c5c824f3969ffc20918468bce55743 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:43 +0900 Subject: [PATCH 0054/1932] New translations common.yml (Norwegian) --- no/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 no/common.yml diff --git a/no/common.yml b/no/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/no/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 4e4f1a8c2e463a1c61a63d796cba4523b7805962 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:44 +0900 Subject: [PATCH 0055/1932] New translations common.yml (Polish) --- pl/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 pl/common.yml diff --git a/pl/common.yml b/pl/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/pl/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 6855c74d92f111f95c350f02676b0b7e89a7bc4c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:45 +0900 Subject: [PATCH 0056/1932] New translations common.yml (Portuguese) --- pt/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 pt/common.yml diff --git a/pt/common.yml b/pt/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/pt/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 5cf6cc1b8784bf71529dd7e790b6d94a306b3a38 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:46 +0900 Subject: [PATCH 0057/1932] New translations common.yml (Russian) --- ru/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 ru/common.yml diff --git a/ru/common.yml b/ru/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/ru/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 68cb83d86ae3e6b97c0e13daafbf4f1b4da62edb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:47 +0900 Subject: [PATCH 0058/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 sr/common.yml diff --git a/sr/common.yml b/sr/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/sr/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From bab758b591ba12abe7f97a9db2d80b667972c448 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:48 +0900 Subject: [PATCH 0059/1932] New translations common.yml (Turkish) --- tr/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 tr/common.yml diff --git a/tr/common.yml b/tr/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/tr/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 1a9169f314c8ace851b72577ec46719e47198cfd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:49 +0900 Subject: [PATCH 0060/1932] New translations common.yml (Hungarian) --- hu/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 hu/common.yml diff --git a/hu/common.yml b/hu/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/hu/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 3562518ffdc64c310e613252dd767b68a21f0807 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:50 +0900 Subject: [PATCH 0061/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 uk/common.yml diff --git a/uk/common.yml b/uk/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/uk/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 34af3e003d1b95d2e456c0aacee783bbe638489d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:51 +0900 Subject: [PATCH 0062/1932] New translations common.yml (Chinese Simplified) --- zh/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 zh/common.yml diff --git a/zh/common.yml b/zh/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/zh/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From beb011b8baacd2b67ec62926b9984f0abed7b7db Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:53 +0900 Subject: [PATCH 0063/1932] New translations common.yml (English) --- en/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 en/common.yml diff --git a/en/common.yml b/en/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/en/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From b0783ad54ae119107e26ee13d8886224266ed924 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:54 +0900 Subject: [PATCH 0064/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 vi/common.yml diff --git a/vi/common.yml b/vi/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/vi/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 932a81bd998d33737c07cd023ee77e0d2664945e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:56 +0900 Subject: [PATCH 0065/1932] New translations homepage.yml (Romanian) --- ro/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 ro/homepage.yml diff --git a/ro/homepage.yml b/ro/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/ro/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 83a818984865036011ff5c875e949d491a64bc0f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:57 +0900 Subject: [PATCH 0066/1932] New translations homepage.yml (French) --- fr/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 fr/homepage.yml diff --git a/fr/homepage.yml b/fr/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/fr/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 27ff7bd5d485ccf27c8bccc275d958a2d02596c5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:58 +0900 Subject: [PATCH 0067/1932] New translations common.yml (Italian) --- it/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 it/common.yml diff --git a/it/common.yml b/it/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/it/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 145f052fcb5d0bf1ab1a850552a661247b5f220a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:01:59 +0900 Subject: [PATCH 0068/1932] New translations common.yml (Korean) --- ko/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 ko/common.yml diff --git a/ko/common.yml b/ko/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/ko/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From f46ba006e7fb08e5f5f78ad76ed40505e1d6ba94 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:01 +0900 Subject: [PATCH 0069/1932] New translations common.yml (Hebrew) --- he/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 he/common.yml diff --git a/he/common.yml b/he/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/he/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 5c795686ee5c45307279ddfd525f324662b128aa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:02 +0900 Subject: [PATCH 0070/1932] New translations common.yml (Romanian) --- ro/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 ro/common.yml diff --git a/ro/common.yml b/ro/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/ro/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 30915e70678e82dce610c8f87bb7c7db7e175e9b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:03 +0900 Subject: [PATCH 0071/1932] New translations accounts.yml (Swedish) --- sv/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 sv/accounts.yml diff --git a/sv/accounts.yml b/sv/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/sv/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From cbb795703d6c879ce3242dba8f5991cdb5840e6f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:04 +0900 Subject: [PATCH 0072/1932] New translations accounts.yml (Turkish) --- tr/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 tr/accounts.yml diff --git a/tr/accounts.yml b/tr/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/tr/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From af70b9d0f067fae2af0e46c73a97602a31d0d7e2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:05 +0900 Subject: [PATCH 0073/1932] New translations accounts.yml (Ukrainian) --- uk/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 uk/accounts.yml diff --git a/uk/accounts.yml b/uk/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/uk/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 976e05eb53673ea1e5930a2ce504768d61508fc0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:06 +0900 Subject: [PATCH 0074/1932] New translations accounts.yml (Chinese Simplified) --- zh/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 zh/accounts.yml diff --git a/zh/accounts.yml b/zh/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/zh/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From da6920592d7dc641acd4e4ae01a5444fe222bd64 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:08 +0900 Subject: [PATCH 0075/1932] New translations common.yml (Finnish) --- fi/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 fi/common.yml diff --git a/fi/common.yml b/fi/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/fi/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 40f0634f778085f6f2ff0ee2d832f2bf04225d2f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:08 +0900 Subject: [PATCH 0076/1932] New translations accounts.yml (Vietnamese) --- vi/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 vi/accounts.yml diff --git a/vi/accounts.yml b/vi/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/vi/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From fe3de03174f315f90ad7485196df5d4b0228651d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:10 +0900 Subject: [PATCH 0077/1932] New translations accounts.yml (English) --- en/accounts.yml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 en/accounts.yml diff --git a/en/accounts.yml b/en/accounts.yml new file mode 100644 index 00000000000..03c4279ca1f --- /dev/null +++ b/en/accounts.yml @@ -0,0 +1,115 @@ +--- +locale: en-US +translations: + - + key: accounts.error_incorrect_password + t: Incorrect password + - + key: accounts.error_email_required + t: Email required + - + key: accounts.error_email_already_exists + t: Email already exists + - + key: accounts.error_invalid_email + t: Invalid email + - + key: accounts.error_minchar + t: Your password is too short + - + key: accounts.error_unknown + t: Unknown error + - + key: accounts.error_user_not_found + t: User not found + - + key: accounts.error_username_already_exists + t: Username already exists + - + key: accounts.enter_username_or_email + t: Enter username or email + - + key: accounts.error_internal_server_error + t: Internal server error + - + key: accounts.error_token_expired + t: Invalid password reset token + - + key: accounts.username_or_email + t: Username or email + - + key: accounts.enter_username + t: Enter username + - + key: accounts.username + t: Username + - + key: accounts.enter_email + t: Enter email + - + key: accounts.email + t: Email + - + key: accounts.enter_password + t: Enter password + - + key: accounts.password + t: Password + - + key: accounts.choose_password + t: Choose password + - + key: accounts.change_password + t: Change password + - + key: accounts.reset_your_password + t: Reset your password + - + key: accounts.set_password + t: Set password + - + key: accounts.enter_new_password + t: Enter new password + - + key: accounts.new_password + t: New password + - + key: accounts.forgot_password + t: Forgot password + - + key: accounts.sign_up + t: Sign up + - + key: accounts.sign_in + t: Log in + - + key: accounts.switch_to_sign_up + t: Don't have an account ? Sign up + - + key: accounts.switch_to_sign_in + t: Already have an account? Log in + - + key: accounts.sign_out + t: Sign out + - + key: accounts.cancel + t: Cancel + - + key: accounts.info_email_sent + t: Email sent. + - + key: accounts.info_password_changed + t: Password changed. + - + key: accounts.please_pick_password + t: Please pick a new password to continue. + - + key: accounts.please_log_in + t: Please log in or sign up to begin. + - + key: accounts.logged_in_as + t: Logged in as {email} + - + key: accounts.questions + t: > + If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. From 7f935b1eb481907da7217a5bc90339c8846057ac Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:11 +0900 Subject: [PATCH 0078/1932] New translations common.yml (French) --- fr/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 fr/common.yml diff --git a/fr/common.yml b/fr/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/fr/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From f22fbb1e43bd6f00d0a4513f24c028c48ea05014 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:12 +0900 Subject: [PATCH 0079/1932] New translations common.yml (Danish) --- da/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 da/common.yml diff --git a/da/common.yml b/da/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/da/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From e797330c88f8fabda098ee4a1673c40596a7b87b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:13 +0900 Subject: [PATCH 0080/1932] New translations common.yml (Spanish) --- es/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 es/common.yml diff --git a/es/common.yml b/es/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/es/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 967641f7eb9aea2804735e46d09efab267d88b5f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:14 +0900 Subject: [PATCH 0081/1932] New translations common.yml (German) --- de/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 de/common.yml diff --git a/de/common.yml b/de/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/de/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 363a7aa7894363e86315c4e5e006e8a3b14065e0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:15 +0900 Subject: [PATCH 0082/1932] New translations common.yml (Greek) --- el/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 el/common.yml diff --git a/el/common.yml b/el/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/el/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 04dca70907256edd9f59fb082e4a9e3debf8ec52 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:16 +0900 Subject: [PATCH 0083/1932] New translations common.yml (Czech) --- cs/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 cs/common.yml diff --git a/cs/common.yml b/cs/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/cs/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 62c0e2af216975d9e137f864210d167d678d7fcf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:17 +0900 Subject: [PATCH 0084/1932] New translations common.yml (Catalan) --- ca/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 ca/common.yml diff --git a/ca/common.yml b/ca/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/ca/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From 69acd45ee430370d05752cb3c8b4e272dee55e2b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:18 +0900 Subject: [PATCH 0085/1932] New translations common.yml (Arabic) --- ar/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 ar/common.yml diff --git a/ar/common.yml b/ar/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/ar/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From a092aaad761967be1a81972d7522911e5ac72841 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:19 +0900 Subject: [PATCH 0086/1932] New translations common.yml (Afrikaans) --- af/common.yml | 1416 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1416 insertions(+) create mode 100644 af/common.yml diff --git a/af/common.yml b/af/common.yml new file mode 100644 index 00000000000..a2c3447fb70 --- /dev/null +++ b/af/common.yml @@ -0,0 +1,1416 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! + Your data is saved. You can review or modify it until the survey closes. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: Under 10 years old + - + key: options.age.range_10_18 + t: 10-18 years old + - + key: options.age.range_18_24 + t: 18-24 years old + - + key: options.age.range_25_34 + t: 24-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<10' + - + key: options.age.range_10_18.short + t: 10-18 + - + key: options.age.range_18_24.short + t: 18-24 + - + key: options.age.range_25_34.short + t: 24-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 2 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 5 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 10 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 2-5 years + - + key: options.years_of_experience.range_5_10.short + t: 5-10 years + - + key: options.years_of_experience.range_10_20.short + t: 10-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 1 to 5 employees + - + key: options.company_size.range_5_10 + t: 5 to 10 employees + - + key: options.company_size.range_10_20 + t: 10 to 20 employees + - + key: options.company_size.range_20_50 + t: 20 to 50 employees + - + key: options.company_size.range_50_100 + t: 50 to 100 employees + - + key: options.company_size.range_100_1000 + t: 100 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 5-10 + - + key: options.company_size.range_10_20.short + t: 10-20 + - + key: options.company_size.range_20_50.short + t: 20-50 + - + key: options.company_size.range_50_100.short + t: 50-100 + - + key: options.company_size.range_100_1000.short + t: 100-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #job titles + key: options.job_title.cto + t: CTO + - + key: options.job_title.front_end_developer + t: Front End Developer/Engineer + - + key: options.job_title.back_end_developer + t: Back End Developer/Engineer + - + key: options.job_title.full_stack_developer + t: Full Stack Developer/Engineer + - + key: options.job_title.web_developer + t: Web Developer + - + key: options.job_title.web_designer + t: Web Designer + - + key: options.job_title.ux_designer + t: UX Designer + - + key: options.job_title.ui_designer + t: UI Designer + - + key: options.job_title.back_end_dev + t: Back-end Developer/Engineer + - + #JavaScript proficiency + key: options.javascript_proficiency.0 + t: Not able to write any JavaScript + - + key: options.javascript_proficiency.1 + t: Writing short, simple JavaScript or jQuery statements + - + key: options.javascript_proficiency.2 + t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) + - + key: options.javascript_proficiency.3 + t: Architecturing entire front-end codebases from scratch + - + key: options.javascript_proficiency.4 + t: Handling advanced front-end patterns (state management, data loading, etc.) + - + #CSS proficiency + key: options.css_proficiency.0 + t: Virtually no knowledge of CSS + - + key: options.css_proficiency.1 + t: Using CSS frameworks and tweaking existing styles + - + key: options.css_proficiency.2 + t: Knowing specificity rules, being able to create layouts + - + key: options.css_proficiency.3 + t: Mastering animations, interactions, transitions, etc. + - + key: options.css_proficiency.4 + t: Able to style an entire front-end from scratch following a consistent methodology + - + #Back-end proficiency + key: options.backend_proficiency.0 + t: Not able to handle any back-end work + - + key: options.backend_proficiency.1 + t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) + - + key: options.backend_proficiency.2 + t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) + - + key: options.backend_proficiency.3 + t: Setting up an entire back-end from scratch (Go, Node.js, etc.) + - + key: options.backend_proficiency.4 + t: Able to handle complex multi-server or microservices architectures + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #learning method + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). From a2580e0c2f787e4e3f3e0476fb97ea3ce47e2262 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:20 +0900 Subject: [PATCH 0087/1932] New translations homepage.yml (Spanish) --- es/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 es/homepage.yml diff --git a/es/homepage.yml b/es/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/es/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From a838860ea7812eaebe709cf551d822bae9adb736 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:21 +0900 Subject: [PATCH 0088/1932] New translations homepage.yml (Afrikaans) --- af/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 af/homepage.yml diff --git a/af/homepage.yml b/af/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/af/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 8d7a58aa2e041db4a6462522e8ffc5c12a188a39 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:22 +0900 Subject: [PATCH 0089/1932] New translations homepage.yml (Arabic) --- ar/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 ar/homepage.yml diff --git a/ar/homepage.yml b/ar/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/ar/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 6217ee5abafe35d9023558e5c3592f31f31eedc9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:22 +0900 Subject: [PATCH 0090/1932] New translations homepage.yml (Catalan) --- ca/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 ca/homepage.yml diff --git a/ca/homepage.yml b/ca/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/ca/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 33228cf3df53f23c662e876c1bcbebf2ed252bd7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:23 +0900 Subject: [PATCH 0091/1932] New translations homepage.yml (Czech) --- cs/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 cs/homepage.yml diff --git a/cs/homepage.yml b/cs/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/cs/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 4e40cf297ed682583121a23b5d559f640f07230e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:24 +0900 Subject: [PATCH 0092/1932] New translations homepage.yml (Danish) --- da/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 da/homepage.yml diff --git a/da/homepage.yml b/da/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/da/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 0c304bebf4864ee6f37b97e09b1179bf54d124b1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:25 +0900 Subject: [PATCH 0093/1932] New translations homepage.yml (German) --- de/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 de/homepage.yml diff --git a/de/homepage.yml b/de/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/de/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 36bba1261f6d802862eb4af9e5f1339959851646 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:26 +0900 Subject: [PATCH 0094/1932] New translations homepage.yml (Greek) --- el/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 el/homepage.yml diff --git a/el/homepage.yml b/el/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/el/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From c61b50aacd46bc6bd14306b31e481e6c936a6526 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:27 +0900 Subject: [PATCH 0095/1932] New translations homepage.yml (Finnish) --- fi/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 fi/homepage.yml diff --git a/fi/homepage.yml b/fi/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/fi/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 0f8c17b703cf3533edfb1226a85ce61ab0580ba4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:27 +0900 Subject: [PATCH 0096/1932] New translations how_to_help.yml (Norwegian) --- no/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 no/how_to_help.yml diff --git a/no/how_to_help.yml b/no/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/no/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 7eea4fc04dea419b1c5a8ed0a48a60a1b553cd85 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:28 +0900 Subject: [PATCH 0097/1932] New translations how_to_help.yml (German) --- de/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 de/how_to_help.yml diff --git a/de/how_to_help.yml b/de/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/de/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 7d0159bb881df4eaff727562de5dec0c3152a53d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:29 +0900 Subject: [PATCH 0098/1932] New translations how_to_help.yml (Greek) --- el/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 el/how_to_help.yml diff --git a/el/how_to_help.yml b/el/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/el/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 697a24628ddc727e39f5e803649c9636b7431d17 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:30 +0900 Subject: [PATCH 0099/1932] New translations how_to_help.yml (Finnish) --- fi/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 fi/how_to_help.yml diff --git a/fi/how_to_help.yml b/fi/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/fi/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 8f5d187130c171494266532056f61e70eef7b9e5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:31 +0900 Subject: [PATCH 0100/1932] New translations how_to_help.yml (Hebrew) --- he/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 he/how_to_help.yml diff --git a/he/how_to_help.yml b/he/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/he/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 0f68fef34e078dd14dddf4d06bffdf586e631bc1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:32 +0900 Subject: [PATCH 0101/1932] New translations how_to_help.yml (Hungarian) --- hu/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 hu/how_to_help.yml diff --git a/hu/how_to_help.yml b/hu/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/hu/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 3df85bd14bdbcf4ac8d6d00ca357baa05c67cac1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:32 +0900 Subject: [PATCH 0102/1932] New translations how_to_help.yml (Italian) --- it/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 it/how_to_help.yml diff --git a/it/how_to_help.yml b/it/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/it/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From f2eb0b6426787bfad47ea6beabd688c10ee27cc6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:33 +0900 Subject: [PATCH 0103/1932] New translations how_to_help.yml (Japanese) --- ja/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 ja/how_to_help.yml diff --git a/ja/how_to_help.yml b/ja/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/ja/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From feafe11067dfe9ea52cf9d8c5e4939ccaa43f2a1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:34 +0900 Subject: [PATCH 0104/1932] New translations how_to_help.yml (Korean) --- ko/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 ko/how_to_help.yml diff --git a/ko/how_to_help.yml b/ko/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/ko/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 3a0b41741ab096d5b6d3f3b089c075765a0a8f33 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:35 +0900 Subject: [PATCH 0105/1932] New translations how_to_help.yml (Dutch) --- nl/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 nl/how_to_help.yml diff --git a/nl/how_to_help.yml b/nl/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/nl/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From f32b75871981b3af8768d9ba042ae3b3023421b0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:36 +0900 Subject: [PATCH 0106/1932] New translations how_to_help.yml (Polish) --- pl/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 pl/how_to_help.yml diff --git a/pl/how_to_help.yml b/pl/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/pl/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From ecac22e01486c32cdd11e6010fb5b60e2ddc6b8a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:37 +0900 Subject: [PATCH 0107/1932] New translations how_to_help.yml (Czech) --- cs/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 cs/how_to_help.yml diff --git a/cs/how_to_help.yml b/cs/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/cs/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 2600e8e95fdb320dda41b8641cee57decabf98e3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:38 +0900 Subject: [PATCH 0108/1932] New translations how_to_help.yml (Portuguese) --- pt/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 pt/how_to_help.yml diff --git a/pt/how_to_help.yml b/pt/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/pt/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From e0ed8341124773effb26c4486363436cdecfd954 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:38 +0900 Subject: [PATCH 0109/1932] New translations how_to_help.yml (Russian) --- ru/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 ru/how_to_help.yml diff --git a/ru/how_to_help.yml b/ru/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/ru/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 264836b5cef6e7e283b04b54c73a2ade73be455b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:39 +0900 Subject: [PATCH 0110/1932] New translations how_to_help.yml (Serbian (Cyrillic)) --- sr/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 sr/how_to_help.yml diff --git a/sr/how_to_help.yml b/sr/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/sr/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From b5bce167b57d2f1a86ad1dd3ec205d981eb60356 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:40 +0900 Subject: [PATCH 0111/1932] New translations how_to_help.yml (Swedish) --- sv/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 sv/how_to_help.yml diff --git a/sv/how_to_help.yml b/sv/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/sv/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 187be076e0831f95f402ca522fa8f850365eabe8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:41 +0900 Subject: [PATCH 0112/1932] New translations how_to_help.yml (Turkish) --- tr/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 tr/how_to_help.yml diff --git a/tr/how_to_help.yml b/tr/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/tr/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 100625f8be3274d45694c59906414327ab0387dd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:42 +0900 Subject: [PATCH 0113/1932] New translations how_to_help.yml (Ukrainian) --- uk/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 uk/how_to_help.yml diff --git a/uk/how_to_help.yml b/uk/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/uk/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From d05eabaf6011cf8ce72b9492db3314559b5f42d5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:43 +0900 Subject: [PATCH 0114/1932] New translations how_to_help.yml (Chinese Simplified) --- zh/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 zh/how_to_help.yml diff --git a/zh/how_to_help.yml b/zh/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/zh/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 70cb51dcf93fed77f1627a862f9c601b461e5f6b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:45 +0900 Subject: [PATCH 0115/1932] New translations how_to_help.yml (English) --- en/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 en/how_to_help.yml diff --git a/en/how_to_help.yml b/en/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/en/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 6c5acb960314fabcf7fe8706733bf869fefb25dc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:45 +0900 Subject: [PATCH 0116/1932] New translations how_to_help.yml (Vietnamese) --- vi/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 vi/how_to_help.yml diff --git a/vi/how_to_help.yml b/vi/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/vi/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 1c99a66a8e5b93056d4a139d1fd4953f9af2a85b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:46 +0900 Subject: [PATCH 0117/1932] New translations how_to_help.yml (Danish) --- da/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 da/how_to_help.yml diff --git a/da/how_to_help.yml b/da/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/da/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From e07a0aa725da442745b5e016a38f699c7d42ef32 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:47 +0900 Subject: [PATCH 0118/1932] New translations how_to_help.yml (Catalan) --- ca/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 ca/how_to_help.yml diff --git a/ca/how_to_help.yml b/ca/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/ca/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From d0d63b778a68841717f1e71f8ec7887e4d4c93c1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:48 +0900 Subject: [PATCH 0119/1932] New translations homepage.yml (Hebrew) --- he/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 he/homepage.yml diff --git a/he/homepage.yml b/he/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/he/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From cc813c1627450f2e9379bfec10cd416df17a8b59 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:49 +0900 Subject: [PATCH 0120/1932] New translations homepage.yml (Swedish) --- sv/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 sv/homepage.yml diff --git a/sv/homepage.yml b/sv/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/sv/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From b979a4117cc457c7dfc2fc9b67704224bf1f1553 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:50 +0900 Subject: [PATCH 0121/1932] New translations homepage.yml (Hungarian) --- hu/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 hu/homepage.yml diff --git a/hu/homepage.yml b/hu/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/hu/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 39c2ec8f7f05dea27982971bda7672620bd532e0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:51 +0900 Subject: [PATCH 0122/1932] New translations homepage.yml (Italian) --- it/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 it/homepage.yml diff --git a/it/homepage.yml b/it/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/it/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 2fb6c5705e484a4c009f99fed2fb7f4431767ce7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:52 +0900 Subject: [PATCH 0123/1932] New translations homepage.yml (Japanese) --- ja/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 ja/homepage.yml diff --git a/ja/homepage.yml b/ja/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/ja/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 5e065a70dfa739269baac7dc23d95069f875d380 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:53 +0900 Subject: [PATCH 0124/1932] New translations homepage.yml (Korean) --- ko/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 ko/homepage.yml diff --git a/ko/homepage.yml b/ko/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/ko/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From aa810bfea59d06ed66183b78d9e849eefca85131 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:54 +0900 Subject: [PATCH 0125/1932] New translations homepage.yml (Dutch) --- nl/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 nl/homepage.yml diff --git a/nl/homepage.yml b/nl/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/nl/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 88f4fdb2cf340dae59e151d0fc148ae81466e9e8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:55 +0900 Subject: [PATCH 0126/1932] New translations homepage.yml (Norwegian) --- no/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 no/homepage.yml diff --git a/no/homepage.yml b/no/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/no/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 475718ad8d1eb2ad5be5e13ed07261265b65f493 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:55 +0900 Subject: [PATCH 0127/1932] New translations homepage.yml (Polish) --- pl/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 pl/homepage.yml diff --git a/pl/homepage.yml b/pl/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/pl/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From f8800ba929c8fe082e641275f20c5354fb610c39 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:56 +0900 Subject: [PATCH 0128/1932] New translations homepage.yml (Portuguese) --- pt/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 pt/homepage.yml diff --git a/pt/homepage.yml b/pt/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/pt/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 441aab3b6e6aaeb4b188505529372bf61607d3de Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:57 +0900 Subject: [PATCH 0129/1932] New translations homepage.yml (Russian) --- ru/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 ru/homepage.yml diff --git a/ru/homepage.yml b/ru/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/ru/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From e46e4e53a19ae29482003ad01c4fc758f429bcd0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:58 +0900 Subject: [PATCH 0130/1932] New translations homepage.yml (Serbian (Cyrillic)) --- sr/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 sr/homepage.yml diff --git a/sr/homepage.yml b/sr/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/sr/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 86943792a037de5cb94374c5aa28aa7b3d6699a0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:59 +0900 Subject: [PATCH 0131/1932] New translations homepage.yml (Turkish) --- tr/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 tr/homepage.yml diff --git a/tr/homepage.yml b/tr/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/tr/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From ef4f18941da6d708284df17c1abe607f5f27f99f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:02:59 +0900 Subject: [PATCH 0132/1932] New translations how_to_help.yml (Arabic) --- ar/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 ar/how_to_help.yml diff --git a/ar/how_to_help.yml b/ar/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/ar/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 80cbdc215d16cc2a9b776b7d32782e6388f5e010 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:02 +0900 Subject: [PATCH 0133/1932] New translations homepage.yml (Ukrainian) --- uk/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 uk/homepage.yml diff --git a/uk/homepage.yml b/uk/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/uk/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 1d03b4d302c5b315ef67b16b11811ece9866f66c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:03 +0900 Subject: [PATCH 0134/1932] New translations homepage.yml (Chinese Simplified) --- zh/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 zh/homepage.yml diff --git a/zh/homepage.yml b/zh/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/zh/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 57a70ebffa383a5c9b1530ec11b7cd2238f503c1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:04 +0900 Subject: [PATCH 0135/1932] New translations homepage.yml (English) --- en/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 en/homepage.yml diff --git a/en/homepage.yml b/en/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/en/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From ffcc1cbdccfb50dcbaf2c2418a6d9262ac949a31 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:05 +0900 Subject: [PATCH 0136/1932] New translations homepage.yml (Vietnamese) --- vi/homepage.yml | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 vi/homepage.yml diff --git a/vi/homepage.yml b/vi/homepage.yml new file mode 100644 index 00000000000..51bcc5ae5be --- /dev/null +++ b/vi/homepage.yml @@ -0,0 +1,50 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Homepage + ########################################################################### + key: homepage.hand_coded + t: Hand-coded in Japan. + - + key: homepage.leave_issue + t: Leave an issue + - + key: homepage.get_in_touch + t: Get in touch + - + key: homepage.made_by + t: 'The State of CSS is Made by:' + - + key: homepage.previous_years + t: 'Previous Years:' + - + key: homepage.intro + t: > + ## CSS is evolving faster than ever. + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + So after the success of our annual [State Of JavaScript](https://stateofjs.com) survey, we’ve decided to take on the world of styles and selectors to help identify the latest trends… and try to bridge the ever-growing “great front-end divide”! + - + key: homepage.take_survey + t: Take Survey + - + key: homepage.view_results + t: View 2019 Results + - + key: share.help_spread + t: Help Spread the Word! + - + key: newsletter.stay_tuned + t: Stay Tuned + - + key: newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - + key: author.sacha.bio + t: > + Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + - + key: author.raphael.bio + t: > + Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. From 6a634e37515068a0185bacb403d3d6fc209f2c12 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:07 +0900 Subject: [PATCH 0137/1932] New translations how_to_help.yml (Romanian) --- ro/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 ro/how_to_help.yml diff --git a/ro/how_to_help.yml b/ro/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/ro/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From a62df21af685bcecb5a94815dbe717696c3bd9ed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:07 +0900 Subject: [PATCH 0138/1932] New translations how_to_help.yml (French) --- fr/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 fr/how_to_help.yml diff --git a/fr/how_to_help.yml b/fr/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/fr/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 57f82937cb5704ff2544809a94e1f3d7315bff4f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:08 +0900 Subject: [PATCH 0139/1932] New translations how_to_help.yml (Spanish) --- es/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 es/how_to_help.yml diff --git a/es/how_to_help.yml b/es/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/es/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From d9a89aa2484004848612b0281f7a8eaeeb5e9503 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:09 +0900 Subject: [PATCH 0140/1932] New translations how_to_help.yml (Afrikaans) --- af/how_to_help.yml | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 af/how_to_help.yml diff --git a/af/how_to_help.yml b/af/how_to_help.yml new file mode 100644 index 00000000000..54321e8f3bf --- /dev/null +++ b/af/how_to_help.yml @@ -0,0 +1,40 @@ +--- +locale: en-US +translations: + - + key: how_to_help.content + t: > + Although the State of JavaScript and CSS do earn some revenue, they still rely primarily on volunteer work. If you'd like to join the project and help out, here are a few things we always need help with. + ### Translation + The surveys are now translated in 20+ languages, but a lot of the translations are incomplete or out of date. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs) and give your GitHub username in the **#translations** channel. + ### Outreach + It's no secret that audiences for developer surveys in general tend to skew male, white, and U.S.-based. If you'd like to help us balance things out a bit, we could definitely use your help! + Outreach efforts include things like reaching out to organizations focused on helping minoritized populations negotiate the tech world, submitting links to the survey to various online communities, emailing blogs or magazines about the survey, and generally trying to diversify the survey's audience. If you'd like to help, [join our Discord](https://discord.gg/tuWRUWVyJs)'s **#outreach** channel (feel free to mute every other channel if you'd like). + Specifically, we'd love some help reaching out to organizations focused on: + + - BIPOC developers + + - LGBTQ+ developers + + - Women developers + + - Developers with disabilities + + - Developers in under-represented countries (China, Brazil, India, Japan, etc.) + + ### Writing & Analysis + Even though we try and surface interesting insights every year, we know there is no way to cover everything in a single report. If you're a data scientist or just curious about tech trends, we would love to see your own spin on our data! This can be a great way to broaden the dialog around the survey, especially when it comes to highlighting under-represented communities like the ones mentioned above. + You can either use the chart customization feature (pencil icon next to some charts) and our [public GraphQL API](https://api.stateofjs.com/) to create new visualizations, or [join our Discord](https://discord.gg/tuWRUWVyJs) and get in touch to ask for the full JSON dataset. + ### Coding + The entirety of our codebases are open-source, and we welcome contributions. I suggest first [getting familiar with how the surveys are run](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb), and then [dropping by the Discord](https://discord.gg/tuWRUWVyJs) to let me know what you'd like to work on. + #### A Note About Paid Work + I have talked mainly about volunteer work here but we also have a small budget to pay consultants or experts, and are working on finding partners to subsidize more work. More specifically, we prefer paying for tasks that: + + - Are **limited in scope**, since the budget will probably be limited too. + + - Require **special expertise** that would not be easily provided by volunteers. + + - Are **self-contained** and don't require too much follow-up work since we might not have time to do it. + + Good examples include: illustrations & branding work, usability or accessibility audits, data visualization work, outreach work, etc. + So although we can't promise much, if you'd like to contribute to the project but can't afford to work on a volunteer basis, don't hesitate to [join the Discord](https://discord.gg/tuWRUWVyJs) and get in touch! From 94c7be6038e110f0c3c298ee132bef157c20f569 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:11 +0900 Subject: [PATCH 0141/1932] New translations results.yml (Romanian) --- ro/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 ro/results.yml diff --git a/ro/results.yml b/ro/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/ro/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 8eaa9baec30b293003be595fc79b5fd0ce90f347 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:12 +0900 Subject: [PATCH 0142/1932] New translations state_of_css.yml (Danish) --- da/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 da/state_of_css.yml diff --git a/da/state_of_css.yml b/da/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/da/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 39d9086b14377b70f36bb73d00a8b9e3921e89c6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:13 +0900 Subject: [PATCH 0143/1932] New translations results.yml (Vietnamese) --- vi/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 vi/results.yml diff --git a/vi/results.yml b/vi/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/vi/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 01d0ff6c2af5362d93fc923c9f2e22c8c0a075f0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:14 +0900 Subject: [PATCH 0144/1932] New translations results.yml (Portuguese, Brazilian) --- pt/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 pt/results.yml diff --git a/pt/results.yml b/pt/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/pt/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 655e45dbb37cb06cd6f687301033ef844d3dff41 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:15 +0900 Subject: [PATCH 0145/1932] New translations state_of_css.yml (Romanian) --- ro/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 ro/state_of_css.yml diff --git a/ro/state_of_css.yml b/ro/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/ro/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 16f8ec569f34d58dffc8a352be3955503157aac2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:16 +0900 Subject: [PATCH 0146/1932] New translations state_of_css.yml (French) --- fr/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 fr/state_of_css.yml diff --git a/fr/state_of_css.yml b/fr/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/fr/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 2baa66cd55b281bb51481bc3aa7731b5d4c2f4f5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:17 +0900 Subject: [PATCH 0147/1932] New translations state_of_css.yml (Spanish) --- es/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 es/state_of_css.yml diff --git a/es/state_of_css.yml b/es/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/es/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From d9a2011b5efc82a4fea96824b7e588732e12c30f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:18 +0900 Subject: [PATCH 0148/1932] New translations state_of_css.yml (Afrikaans) --- af/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 af/state_of_css.yml diff --git a/af/state_of_css.yml b/af/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/af/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 3c71167c5747585daecd7180bf048c27ff518e6c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:19 +0900 Subject: [PATCH 0149/1932] New translations state_of_css.yml (Arabic) --- ar/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 ar/state_of_css.yml diff --git a/ar/state_of_css.yml b/ar/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/ar/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 30923ec8bf517318551f158175da82032aa5140f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:20 +0900 Subject: [PATCH 0150/1932] New translations state_of_css.yml (Catalan) --- ca/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 ca/state_of_css.yml diff --git a/ca/state_of_css.yml b/ca/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/ca/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 709bb046109f0f453d1aee3161792cfd6b702e4d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:21 +0900 Subject: [PATCH 0151/1932] New translations state_of_css.yml (Czech) --- cs/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 cs/state_of_css.yml diff --git a/cs/state_of_css.yml b/cs/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/cs/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From d12be1f604ef802ca64c19ab01a508d7590d6940 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:22 +0900 Subject: [PATCH 0152/1932] New translations state_of_css.yml (German) --- de/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 de/state_of_css.yml diff --git a/de/state_of_css.yml b/de/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/de/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From ee6c32dc7eef859abf672755203a4c33dba9bcc4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:23 +0900 Subject: [PATCH 0153/1932] New translations results.yml (Chinese Traditional) --- zh/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 zh/results.yml diff --git a/zh/results.yml b/zh/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/zh/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 19561d6c4b654e3057a6539f9a745d1236886cf8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:24 +0900 Subject: [PATCH 0154/1932] New translations state_of_css.yml (Greek) --- el/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 el/state_of_css.yml diff --git a/el/state_of_css.yml b/el/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/el/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 3a73c9738283804709a07837cf9858aaed991166 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:25 +0900 Subject: [PATCH 0155/1932] New translations state_of_css.yml (Finnish) --- fi/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 fi/state_of_css.yml diff --git a/fi/state_of_css.yml b/fi/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/fi/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 39f365de3b6842f5d79e1fad71368297122fa785 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:26 +0900 Subject: [PATCH 0156/1932] New translations state_of_css.yml (Hebrew) --- he/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 he/state_of_css.yml diff --git a/he/state_of_css.yml b/he/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/he/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From d20fbf03b74071896bd294336030437af9f32457 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:28 +0900 Subject: [PATCH 0157/1932] New translations state_of_css.yml (Hungarian) --- hu/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 hu/state_of_css.yml diff --git a/hu/state_of_css.yml b/hu/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/hu/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From f771ae8ced7c032cac19203fa7bb187aa3590c1f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:29 +0900 Subject: [PATCH 0158/1932] New translations state_of_css.yml (Italian) --- it/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 it/state_of_css.yml diff --git a/it/state_of_css.yml b/it/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/it/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From f36280653b19f67b2df45abdbe879c9dae61a63e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:30 +0900 Subject: [PATCH 0159/1932] New translations state_of_css.yml (Japanese) --- ja/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 ja/state_of_css.yml diff --git a/ja/state_of_css.yml b/ja/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/ja/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 8664791b56f8dd83f28e471f0670a2062cdac13d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:31 +0900 Subject: [PATCH 0160/1932] New translations state_of_css.yml (Korean) --- ko/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 ko/state_of_css.yml diff --git a/ko/state_of_css.yml b/ko/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/ko/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From d98f9bdc4a8ff42e6d149af495775b72224c6f6b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:32 +0900 Subject: [PATCH 0161/1932] New translations state_of_css.yml (Dutch) --- nl/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 nl/state_of_css.yml diff --git a/nl/state_of_css.yml b/nl/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/nl/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From bfc7e81546bda31bfdad72c58ca3d46f1bdd1909 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:33 +0900 Subject: [PATCH 0162/1932] New translations state_of_css.yml (Norwegian) --- no/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 no/state_of_css.yml diff --git a/no/state_of_css.yml b/no/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/no/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 392da68f41b84fab153bda3948236274f24dc039 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:34 +0900 Subject: [PATCH 0163/1932] New translations state_of_css.yml (Polish) --- pl/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 pl/state_of_css.yml diff --git a/pl/state_of_css.yml b/pl/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/pl/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From a2668f970bf00645aa4d4d5f45b9c3a5afc6fd3b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:34 +0900 Subject: [PATCH 0164/1932] New translations results.yml (English) --- en/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 en/results.yml diff --git a/en/results.yml b/en/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/en/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 748e71c49e8c520e8d23213a0205ea83547d254f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:36 +0900 Subject: [PATCH 0165/1932] New translations results.yml (French) --- fr/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 fr/results.yml diff --git a/fr/results.yml b/fr/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/fr/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 4a774339801d90d3b04f7473ecddf5675e8cc70c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:37 +0900 Subject: [PATCH 0166/1932] New translations results.yml (Hungarian) --- hu/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 hu/results.yml diff --git a/hu/results.yml b/hu/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/hu/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 492bcbe12472157cb5a36099218b6c4d6f877ecf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:38 +0900 Subject: [PATCH 0167/1932] New translations results.yml (Spanish) --- es/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 es/results.yml diff --git a/es/results.yml b/es/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/es/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From e26cf69326560b588230cca244fd71d5dbf504a0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:39 +0900 Subject: [PATCH 0168/1932] New translations results.yml (Afrikaans) --- af/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 af/results.yml diff --git a/af/results.yml b/af/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/af/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 363f15d2078e582d0f123e8947c28e234beff667 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:40 +0900 Subject: [PATCH 0169/1932] New translations results.yml (Arabic) --- ar/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 ar/results.yml diff --git a/ar/results.yml b/ar/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/ar/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From cb7349559d9f8abd7d67d180ce506f914fa51f28 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:42 +0900 Subject: [PATCH 0170/1932] New translations results.yml (Catalan) --- ca/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 ca/results.yml diff --git a/ca/results.yml b/ca/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/ca/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From deb30988e2c934cbeecc498e52af153e3fac3fd7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:43 +0900 Subject: [PATCH 0171/1932] New translations results.yml (Czech) --- cs/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 cs/results.yml diff --git a/cs/results.yml b/cs/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/cs/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From e40b1896f0bdd1e8353b162e7ee591f719bbc664 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:44 +0900 Subject: [PATCH 0172/1932] New translations results.yml (Danish) --- da/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 da/results.yml diff --git a/da/results.yml b/da/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/da/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 589d1d513a8dbebe87f301f89940be78f894ed93 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:45 +0900 Subject: [PATCH 0173/1932] New translations results.yml (German) --- de/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 de/results.yml diff --git a/de/results.yml b/de/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/de/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From aa1c205b22602942cbf269a8c500d201d39b5940 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:46 +0900 Subject: [PATCH 0174/1932] New translations results.yml (Greek) --- el/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 el/results.yml diff --git a/el/results.yml b/el/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/el/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 2b16326da6433f6c3babe4c73c6ae8793a7e152b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:47 +0900 Subject: [PATCH 0175/1932] New translations results.yml (Finnish) --- fi/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 fi/results.yml diff --git a/fi/results.yml b/fi/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/fi/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 20e70f56ecb9cd32103175259e42e556b87940af Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:48 +0900 Subject: [PATCH 0176/1932] New translations results.yml (Hebrew) --- he/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 he/results.yml diff --git a/he/results.yml b/he/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/he/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From bd8cd32f92f0a60ff4cba2764105de804df99f85 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:49 +0900 Subject: [PATCH 0177/1932] New translations results.yml (Italian) --- it/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 it/results.yml diff --git a/it/results.yml b/it/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/it/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 455047a61e8f18f487da58d06a416a7ec63bb113 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:50 +0900 Subject: [PATCH 0178/1932] New translations results.yml (Ukrainian) --- uk/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 uk/results.yml diff --git a/uk/results.yml b/uk/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/uk/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 054e91cb429921b97a9bf318a4fb6354c47ee91b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:51 +0900 Subject: [PATCH 0179/1932] New translations results.yml (Japanese) --- ja/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 ja/results.yml diff --git a/ja/results.yml b/ja/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/ja/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 28da6c0053b50eceb3ade1804ca2d94e2f852946 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:52 +0900 Subject: [PATCH 0180/1932] New translations results.yml (Korean) --- ko/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 ko/results.yml diff --git a/ko/results.yml b/ko/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/ko/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 2a5b88618b89297a4d6f267b1163187a6a957876 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:53 +0900 Subject: [PATCH 0181/1932] New translations results.yml (Dutch) --- nl/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 nl/results.yml diff --git a/nl/results.yml b/nl/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/nl/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 0f7c7a626590eabf18ca980ea25226efc46f4707 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:54 +0900 Subject: [PATCH 0182/1932] New translations results.yml (Norwegian) --- no/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 no/results.yml diff --git a/no/results.yml b/no/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/no/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From df33c03685eedcd3e7a2e475e0fe06f2752d9ca4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:55 +0900 Subject: [PATCH 0183/1932] New translations results.yml (Polish) --- pl/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 pl/results.yml diff --git a/pl/results.yml b/pl/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/pl/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 9046b3c6cf06101320b0490cc182dc7cb5223179 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:57 +0900 Subject: [PATCH 0184/1932] New translations results.yml (Russian) --- ru/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 ru/results.yml diff --git a/ru/results.yml b/ru/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/ru/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 53b499d6a88c7abae2e05d530826ab67551901a7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:58 +0900 Subject: [PATCH 0185/1932] New translations results.yml (Serbian (Cyrillic)) --- sr/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 sr/results.yml diff --git a/sr/results.yml b/sr/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/sr/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 2ded4aeab10824255b342772fa0f4db22af5f0e5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:03:58 +0900 Subject: [PATCH 0186/1932] New translations results.yml (Swedish) --- sv/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 sv/results.yml diff --git a/sv/results.yml b/sv/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/sv/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From 36192d22c588ce2054965db5e7bff906e1c2ead9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:00 +0900 Subject: [PATCH 0187/1932] New translations results.yml (Turkish) --- tr/results.yml | 1211 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1211 insertions(+) create mode 100644 tr/results.yml diff --git a/tr/results.yml b/tr/results.yml new file mode 100644 index 00000000000..552cbddd626 --- /dev/null +++ b/tr/results.yml @@ -0,0 +1,1211 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: results.start + t: Start + - + key: page.previous + t: "Previous:" + - + key: page.next + t: "Next:" + - + key: general.state_of_css_link + t: State of CSS + - + key: general.netlify_link + t: Hosted by Netlify. + - + key: general.completion_percentage + t: "Completion percentage:" + - + key: partners.thanks + t: Thanks to our partners for supporting us! + - + key: partners.learn_more + t: Learn more. + - + key: tabs.all_respondents + t: All Respondents + - + key: tabs.main_answers + t: Main Answers + - + key: tabs.other_answers + t: Other Answers + - + key: tabs.bracket_wins + t: Wins + - + key: tabs.bracket_matchups + t: Matchups + - + key: tabs.chart + t: Chart + - + key: tabs.data + t: Data + - + key: tabs.share + t: Share + - + key: tabs.debug + t: Debug + - + key: tabs.by_country + t: By Country + - + key: tabs.by_experience + t: By Experience + - + key: tabs.by_degree + t: By Degree + - + key: tabs.by_salary + t: By Salary + - + key: tabs.by_gender + t: By Gender + - + ########################################################################### + #Block + ########################################################################### + key: block.data_from + t: foo + - + ########################################################################### + #Options + ########################################################################### + key: options.experience_ranking.satisfaction + t: Satisfaction + - + key: options.experience_ranking.interest + t: Interest + - + key: options.experience_ranking.usage + t: Usage + - + key: options.experience_ranking.awareness + t: Awareness + - + key: options.features_mode.grouped + t: Grouped + - + key: options.features_mode.awareness_rank + t: By Awareness + - + key: options.features_mode.usage_rank + t: By Usage + - + key: options.features_mode.usage_ratio_rank + t: By Usage Ratio + - + key: options.features_simplified.know_it + t: Know about it + - + key: options.features_simplified.used_it + t: Have used it + - + key: options.features_simplified.usage_ratio + t: Usage ratio + - + key: options.quadrant.assess + t: ASSESS + - + key: options.quadrant.assess.long + t: | + ASSESS: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.adopt + t: ADOPT + - + key: options.quadrant.adopt.long + t: | + ADOPT: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.avoid + t: AVOID + - + key: options.quadrant.avoid.long + t: | + AVOID: Low usage, low satisfaction. Technologies probably best avoided currently. + - + key: options.quadrant.analyze + t: ANALYZE + - + key: options.quadrant.analyze.long + t: | + ANALYZE: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: options.quadrant.1 + t: 1 + - + key: options.quadrant.1.long + t: | + 1: Low usage, high satisfaction. Technologies worth keeping an eye on. + - + key: options.quadrant.2 + t: 2 + - + key: options.quadrant.2.long + t: | + 2: High usage, high satisfaction. Safe technologies to adopt. + - + key: options.quadrant.3 + t: 3 + - + key: options.quadrant.3.long + t: | + 3: Low usage, low satisfaction. Technologies that are harder to recommend. + - + key: options.quadrant.4 + t: 4 + - + key: options.quadrant.4.long + t: | + 4: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + key: ranges.selector.years_of_experience + t: Experience + - + key: ranges.selector.yearly_salary + t: Salary + - + key: ranges.selector.company_size + t: Company Size + - + #other learning methods + key: options.first_steps.blogs + t: Blogs + - + key: options.first_steps.forums + t: Forums + - + key: options.first_steps.view_source + t: View Source + - + #other disablities + key: options.disability_status_others.adhd + t: ADHD + - + key: options.disability_status_others.autism + t: Autism + - + key: options.disability_status_others.glasses + t: Glasses + - + key: options.disability_status_others.old + t: Old Age + - + key: options.disability_status_others.back_pain + t: Back Pain + - + key: options.disability_status_others.epilepsy + t: Epilepsy + - + key: options.disability_status_others.aspergers + t: Aspergers + - + key: options.disability_status_others.color_blindness + t: Color Blindness + - + key: options.disability_status_others.anxiety + t: Anxiety + - + key: options.disability_status_others.dyslexia + t: Dyslexia + - + key: options.disability_status_others.diabetes + t: Diabetes + - + key: options.disability_status_others.carpal_tunnel + t: Carpal Tunnel + - + ########################################################################### + #Sections + ########################################################################### + key: sections.introduction.title + t: Introduction + - + key: sections.demographics.title + t: Demographics + - + key: sections.tshirt.title + t: T-shirt + - + key: sections.technologies.title + t: Technologies + - + key: sections.libraries.title + t: Libraries + - + key: sections.conclusion.title + t: Conclusion + - + key: sections.about.title + t: About + - + key: sections.how_to_help.title + t: How to Help + - + key: sections.support.title + t: Support Us + - + key: sections.support.description + t: > + We run this survey as a side project, but in order to make the project sustainable we’re always looking for partners who can help support us, either financially or by helping us spread the word. If you think you could help in any way, please don’t hesitate to [get in touch](mailto:hello@stateofjs.com)! + - + key: sections.awards.title + t: Awards + - + key: sections.awards.description + t: Things that stood out this year. + - + ########################################################################### + #User Info + ########################################################################### + key: user_info.locale + t: Language + - + key: user_info.locale.description + t: What language did respondents select to fill out the survey? + - + key: user_info.locale.note + t: > + This data is collected automatically based on respondent's settings while taking the survey; Languages with fewer than 20 respondents not shown. + - + key: user_info.source + t: Source + - + key: user_info.source.description + t: How did respondents find out about the survey? + - + key: user_info.source.note + t: This data is a mix of self-reported answers, referrer data, and URL tracking data. + - + key: user_info.gender_by_country + t: Gender By Country + - + key: user_info.gender_by_country.description + t: Gender distribution by country with at least 100 respondents, sorted by "mean gender" (each gender key being assigned an integer value in ascending order) descending. + - + key: user_info.years_of_experience_by_salary + t: Years of Experience by Salary Range + - + key: user_info.years_of_experience_by_salary.description + t: Years of experience by salary range. + - + key: user_info.yearly_salary_by_country + t: Salary By Country + - + key: user_info.yearly_salary_by_country.description + t: Yearly salary distribution by country with at least 100 respondents, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_degree + t: Salary By Higher Education Degree + - + key: user_info.yearly_salary_by_degree.description + t: Yearly salary distribution by higher education degree, sorted by mean salary descending. + - + key: user_info.yearly_salary_by_experience + t: Salary By Experience + - + key: user_info.yearly_salary_by_experience.description + t: Yearly salary distribution by experience, sorted by mean salary descending. + - + key: user_info.race_ethnicity_by_years_of_experience + t: Race & Ethnicity by Years of Experience + - + key: user_info.race_ethnicity_by_years_of_experience.description + t: Race & ethnicity distribution by years of experience, sorted by mean experience ascending. + - + key: user_info.higher_education_degree_by_gender + t: Higher Education Degree by Gender + - + key: user_info.higher_education_degree_by_gender.description + t: Higher education degree distribution by gender. + - + ########################################################################### + #Locales + ########################################################################### + key: options.locale.en-US + t: English + - + key: options.locale.ca-ES + t: Catalan + - + key: options.locale.es-ES + t: Spanish + - + key: options.locale.ru-RU + t: Russian + - + key: options.locale.fr-FR + t: French + - + key: options.locale.zh-Hant + t: Chinese (Traditional) + - + key: options.locale.de-DE + t: German + - + key: options.locale.cs-CZ + t: Czech + - + key: options.locale.pt-PT + t: Portuguese + - + key: options.locale.it-IT + t: Italian + - + key: options.locale.sv-SE + t: Swedish + - + key: options.locale.tr-TR + t: Turkish + - + key: options.locale.id-ID + t: Indonesian + - + key: options.locale.hi-IN + t: Hindi + - + key: options.locale.zh-Hans + t: Chinese (Simplified) + - + key: options.locale.ja-JP + t: Japanese + - + key: options.locale.ua-UA + t: Ukrainian + - + key: options.locale.pl-PL + t: Polish + - + key: options.locale.fa-IR + t: Farsi + - + key: options.locale.nl-NL + t: Dutch + - + key: options.locale.ko-KR + t: Korean + - + key: options.locale.ro-RO + t: Romanian + - + ########################################################################### + #Features + ########################################################################### + key: features.learn_more + t: Learn More (MDN) + - + key: features.mdn_link + t: MDN + - + key: features.caniuse_link + t: Can I use + - + key: features.specification_link + t: W3C Specification + - + #knowledge score + key: features.knowledge_score + t: Knowledge Score + - + key: features.knowledge_score.description + t: Out of all the features mentioned in the survey, how many did the respondent know about? + - + ########################################################################### + #Tools & Methodologies + ########################################################################### + #general + key: tools.links + t: Links + - + key: tools.github_link + t: GitHub + - + key: tools.github_stars + t: stars + - + key: tools.homepage_link + t: Homepage + - + key: tools.npm_link + t: NPM + - + key: tools.technology + t: Technology + - + ########################################################################### + #Blocks + ########################################################################### + #heatmaps + key: blocks.tools_company_size_heatmap + t: Usage by Company Size + - + key: blocks.tools_company_size_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different company size ranges. + - + key: blocks.tools_yearly_salary_heatmap + t: Usage by Salary Range + - + key: blocks.tools_yearly_salary_heatmap.description + t: | + For each technology, how usage is spread among respondents + who picked different salary ranges. + - + key: blocks.tools_years_of_experience_heatmap + t: Usage by Years Of Experience + - + key: blocks.tools_years_of_experience_heatmap.description + t: | + For each technology, how usage is spread among respondents who picked different experience ranges. + Note that the experience in question here is general experience, not experience with a specific technology. + - + #tool + key: blocks.entity.homepage_link + t: Homepage + - + key: blocks.entity.github_link + t: GitHub + - + #cardinality + key: blocks.all_sections_tools_cardinality_by_user + t: Technology Usage Cardinality + - + key: blocks.all_sections_tools_cardinality_by_user.description + t: > + For each section, which percentage of respondents **use** (defined as having answered “would use again”) one, two, three, etc. technologies. The bottom-most bar represents the sum of all other bars. + - + key: blocks.cardinality.max + t: Most common answer + - + #tools arrows + key: blocks.tools_arrows + t: Changes Over Time + - + key: blocks.tools_arrows.description + t: | + Each line goes from 2016 to 2020. A higher point means a technology has been used by more people, + and a point further to the right means more users want to learn it; or have used it and would use it again. + - + key: blocks.tools_arrows.note + t: | + - Some lines skip years. + - Technologies with only one year of data are not shown. + - Velocity formula = (most recent opinion - oldest opinion) + (most recent usage) - (oldest usage) + - A positive velocity means the usage and/or positive opinions have increased over time. + - + #tools quadrant + key: blocks.tools_quadrant + t: Satisfaction vs Usage + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **ASSESS**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **ADOPT**: High usage, high satisfaction. Safe technologies to adopt. + + - **AVOID**: Low usage, low satisfaction. Technologies probably best avoided currently. + + - **ANALYZE**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + #category other tools + key: blocks.category_other_tools + t: Other Tools + - + key: blocks.category_other_tools.description + t: Other tools in this category (freeform answers). + - + #tool experience + key: blocks.tool_experience + t: "{name} Experience" + - + key: blocks.tool_experience.description + t: Respondent's experience with {name}. + - + #tool positive/negative split ("marimekko" chart) + key: blocks.tools_experience_marimekko + t: Positive/Negative Split + - + key: blocks.tools_experience_marimekko.description + t: | + This chart splits positive (“want to learn”, “would use again”) vs + negative (“not interested”, “would not use again”) experiences on + both sides of a central axis. + + Bar thickness represents the number of respondents aware of a technology. + - + #tool tier list + key: blocks.tools_tier_list + t: Library Tier List + - + key: blocks.tools_tier_list.description + t: | + This chart ranks libraries based on their satisfaction ratio (percentage of users + who would use a library again). Note that libraries used by less than 10% of survey + respondents are not included. + - + key: blocks.tools_tier_list.bounds + t: > + {lowerBound}% - {upperBound}% + - + #tools section streams + key: blocks.tools_section_streams + t: Experience Over Time + - + key: blocks.tools_section_streams.description + t: | + Overview of opinions on the technologies surveyed over time. + - + key: blocks.tools_section_streams.note + t: | + Technologies with only one year of data are not included. + - + #tools section overview + key: blocks.tools_section_overview + t: Category Overview + - + key: blocks.tools_section_overview.description + t: | + Overview of opinions on the technologies surveyed. Darker segments represent positive opinions, + while lighter segments correspond to negative sentiment. + - + #tools experience ranking + key: blocks.tools_experience_ranking + t: Rankings + - + key: blocks.tools_experience_ranking.description + t: Satisfaction, interest, usage, and awareness ratio rankings. + - + key: blocks.tools_experience_ranking.note + t: | + Technologies with less than 10% awareness not included. Each ratio is defined as follows: + + - Satisfaction: **would use again** / (**would use again** + **would not use again**) + - Interest: **want to learn** / (**want to learn** + **not interested**) + - Usage: (**would use again** + **would not use again**) / **total** + - Awareness: (**total** - **never heard**) / **total** + - + #happiness + key: blocks.happiness + t: Overall Happiness + - + key: blocks.happiness.description + t: | + On a scale of one (very unhappy) to five (very happy), how happy are developers + with the current overall state of this category? + - + #newsletter + key: blocks.newsletter.title + t: Stay Tuned + - + key: blocks.newsletter.description + t: | + If you'd like to know when we release additional results or announce next year's edition, + just leave us your email below: + - + key: blocks.newsletter.email + t: Your Email + - + key: blocks.newsletter.submit + t: Notify Me + - + #features_overview + key: blocks.features_overview + t: Usage Overview + - + key: blocks.features_overview.description + t: | + This chart presents the various adoption rates for all features, grouped by category. + + The size of the outer circle + corresponds to the total number of users who know about a feature, while + the inner one represents those who have actually used it. + + Hover on each node to view detailed data along with an overlay + representing the total number of survey respondents. + - + #export + key: export.export + t: Export + - + key: export.title + t: Export data for {title} + - + key: export.nocsv + t: Sorry, CSV export is not available for this dataset. + - + key: export.graphql + t: > + You can copy paste this query into our public GraphQL API. + - + key: export.export_json + t: Get JSON Data + - + key: export.export_graphql + t: Get GraphQL Query + - + key: custom_data.heading + t: Custom Chart + - + key: custom_data.custom_data + t: Custom Data + - + key: custom_data.graphql_query + t: GraphQL Query + - + key: custom_data.chart_title + t: Custom Chart + - + key: custom_data.submit + t: Submit + - + key: custom_data.empty_contents + t: Please enter some data in the "Custom Data" field. + - + key: custom_data.edit_title + t: Edit Chart Title + - + key: custom_data.customize + t: Customize Data + - + key: custom_data.details + t: > + + 1. Copy the contents of the "GraphQL Query" textfield and paste them into the middle panel of the [GraphQL API explorer](https://graphiql.stateofjs.com/). + 2. Modify the query by adding one or more **filters** using the left-hand explorer sidebar. Make sure to keep the overall structure of the data the same. + 3. In the explorer window, click the Play ("Execute Query") button. + 4. Copy the results of the modified query (`{ data: … }` ) into the "Custom Data" textfield above and submit. + - + #Tools usage variations + key: blocks.tools_usage_variations + t: Usage Variations + - + key: blocks.tools_usage_variations.description + t: | + How different factors such as salary range, years of experience + or company size influence usage (participants who answered either + “would use again” or “would not use again”). + + The baseline represents the base usage for each tool and the offsets + correspond to the delta from this baseline in each range. Let's say + tool X has an overall usage of 10% across all respondents (the baseline), + then if the percentage of users having from 1 to 2 years of experience + using this tool is 13% (compared to all users having from 1 to 2 years + of experience), then we have a positive delta of +3%. + - + key: blocks.tools_usage_variations.note + t: | + Please keep in mind that tools having a lower overall usage tends to vary more. + - + #Recommended Resources + key: blocks.recommended_resources + t: Recommended Resources + - + #Brackets + key: tool_evaluation.tool_evaluation_wins + t: Library Evaluation Rankings + - + key: tool_evaluation.tool_evaluation_wins.description + t: Which factors do you prioritize when evaluating a new library? Results are ranked by number of tournament rounds won. + - + key: tool_evaluation.tool_evaluation_matchups + t: Library Evaluation Rankings (Matchups) + - + key: tool_evaluation.tool_evaluation_matchups.description + t: Which factors do you prioritize when evaluating a new library? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Charts + ########################################################################### + key: chart_units.respondents + t: "{count} question respondents ({percentage}% completion percentage)" + - + key: chart_units.percentage + t: Percents + - + key: chart_units.count + t: Count + - + key: chart_units.percentage_question + t: "% of question respondents" + - + key: chart_units.percentage_survey + t: "% of survey respondents" + - + key: charts.average + t: Average + - + key: charts.mean + t: Mean + - + key: charts.overall + t: Overall + - + key: charts.all_respondents + t: All Respondents + - + key: charts.facet_responses + t: '{count} responses' + - + key: charts.axis_legends.years_of_experience + t: Years of Experience + - + key: charts.axis_legends.yearly_salary + t: Salary Range (USD) + - + key: charts.axis_legends.company_size + t: Number of Employees + - + key: charts.axis_legends.backend_proficiency + t: Back-end Proficiency + - + key: charts.axis_legends.css_proficiency + t: CSS Proficiency + - + key: charts.axis_legends.javascript_proficiency + t: JavaScript Proficiency + - + key: charts.axis_legends.users_percentage + t: Percentage of Users + - + key: charts.axis_legends.users_count + t: User Count + - + key: charts.axis_legends.interest_percentage + t: Interest % + - + key: charts.axis_legends.satisfaction_percentage + t: Satisfaction % + - + key: charts.axis_legends.usage_percentage + t: Usage % + - + key: charts.axis_legends.awareness_percentage + t: Awareness % + - + key: charts.axis_legends.happiness + t: Happiness + - + key: charts.axis_legends.knowledge_score + t: Known Features + - + key: charts.axis_legends.frequency + t: Frequency + - + key: charts.axis_legends.age + t: Age + - + key: charts.axis_legends.users_percentage_survey + t: "% of survey respondents" + - + key: charts.axis_legends.users_percentage_question + t: "% of question respondents" + - + key: charts.ranges_multiple_diverging_lines.baseline + t: baseline + - + key: charts.ranges_multiple_diverging_lines.positive_offset + t: positive offset + - + key: charts.ranges_multiple_diverging_lines.negative_offset + t: negative offset + - + key: charts.tools_arrows.negative_opinion + t: Negative opinions + - + key: charts.tools_arrows.positive_opinion + t: Positive opinions + - + key: charts.tools_arrows.have_not_used + t: Have not used + - + key: charts.tools_arrows.have_used + t: Have used + - + key: charts.tools_arrows.x_axis + t: X-axis range + - + key: charts.tools_arrows.y_axis + t: Y-axis range + - + key: charts.tools_arrows.legend + t: Legend + - + key: charts.tools_arrows.velocity + t: Velocity + - + key: charts.tools_arrows.velocity_positive + t: Overall more positive opinions and/or usage over time + - + key: charts.tools_arrows.velocity_negative + t: Overall more negative opinions and/or less usage over time + - + key: charts.tools_arrows.opinions_positive + t: Mostly positive opinions + - + key: charts.tools_arrows.opinions_negative + t: Mostly negative opinions + - + key: charts.tools_arrows.low_usage + t: Low usage + - + key: charts.tools_arrows.high_usage + t: High usage + - + key: charts.tools_arrows.popularity_positive + t: Rising popularity + - + key: charts.tools_arrows.popularity_negative + t: Falling popularity + - + key: charts.no_answer + t: No Answer + - + ########################################################################### + #Sharing + ########################################################################### + key: share.share + t: Share + - + key: share.options + t: Share Options + - + key: share.preview + t: Social media preview + - + key: share.site.title + t: Discover the {siteTitle} results + - + key: share.site.twitter_text + t: "Discover the {siteTitle} results {link} {hashtag}" + - + key: share.site.subject + t: "{siteTitle} Survey Results" + - + key: share.site.body + t: "Here are some interesting survey results: {link}" + - + key: share.block.twitter_text + t: "{hashtag} {year}: {title} {link}" + - + key: share.block.subject + t: "{siteTitle} Survey Results" + - + key: share.block.body + t: "Here are some interesting survey results ({title}): {link}" + - + key: share.twitter + t: Share on Twitter + - + key: share.facebook + t: Share on Facebook + - + key: share.linkedin + t: Share on LinkedIn + - + key: share.email + t: Share by email + - + key: share.image + t: Get image + - + key: share.link + t: Link to section + - + key: share.url + t: Get link + - + key: share.close + t: Close + - + ########################################################################### + #Views + ########################################################################### + key: views.viz + t: Graph + - + key: views.table + t: Table + - + ########################################################################### + #Tables + ########################################################################### + key: table.label + t: Label + - + key: table.item + t: Item + - + key: table.percentage_survey + t: "% of survey respondents" + - + key: table.percentage_question + t: "% of question respondents" + - + key: table.percentage_facet + t: "% of facet respondents" + - + key: table.count + t: Count + - + key: table.year + t: Year + - + key: table.mean + t: Mean + - + key: table.usage + aliasFor: options.features_simplified.used_it + - + key: table.awareness + aliasFor: options.features_simplified.know_it + - + key: table.usage_ratio + aliasFor: options.features_simplified.usage_ratio + - + key: table.usage_count + aliasFor: charts.axis_legends.users_count + - + key: table.satisfaction_percentage + aliasFor: charts.axis_legends.satisfaction_percentage + - + key: table.interest_percentage + aliasFor: charts.axis_legends.interest_percentage + - + key: table.usage_percentage + aliasFor: charts.axis_legends.usage_percentage + - + key: table.awareness_percentage + aliasFor: charts.axis_legends.awareness_percentage + - + key: table.percentages_table + t: Percentages + - + key: table.rankings_table + t: Rankings + - + key: table.satisfaction_rank + t: Satisfaction Rank + - + key: table.interest_rank + t: Interest Rank + - + key: table.usage_rank + t: Usage Rank + - + key: table.awareness_rank + t: Awareness Rank + - + key: table.would_not_use_percentage + t: Would not use % + - + key: table.not_interested_percentage + t: Not interested % + - + key: table.would_use_percentage + t: Would use again % + - + key: table.interested_percentage + t: Interested % + - + ########################################################################### + #Awards + ########################################################################### + key: awards.runner_ups + t: Runner Ups + - + key: award.feature_adoption_award.title + t: Most Used Feature + - + key: award.feature_adoption_award.description + t: Awarded to the most adopted feature. + - + key: award.feature_adoption_delta_award.title + t: Most Adopted Feature + - + key: award.feature_adoption_delta_award.description + t: Awarded to the feature with the largest year-over-year ”have used” progression. + - + key: award.tool_usage_award.title + t: Most Used Technology + - + key: award.tool_usage_award.description + t: Awarded to the technology with the largest user base. + - + key: award.tool_usage_delta_award.title + t: Most Adopted Technology + - + key: award.tool_usage_delta_award.description + t: Awarded to the technology with the largest year-over-year “would use again” progression. + - + key: award.tool_satisfaction_award.title + t: Highest Satisfaction + - + key: award.tool_satisfaction_award.description + t: Awarded to the technology with the highest percentage of satisfied users. + - + key: award.tool_interest_award.title + t: Highest Interest + - + key: award.tool_interest_award.description + t: Awarded to the technology developers are most interested in learning once they are aware of it. + - + key: award.resource_usage_award.title + t: Most Used Resource + - + key: award.resource_usage_award.description + t: Awarded to the resource with the largest user base. + - + key: award.prediction_award.title + t: Prediction Award + - + key: award.prediction_award.description + t: Awarded to an up-and-coming technology that might take over… or not? + - + key: award.most_write_ins_award.title + t: Most Write-Ins + - + key: award.most_write_ins_award.description + t: Awarded to the item with the most write-in answers + - + ########################################################################### + #Hints + ########################################################################### + key: hints.hint_hint + t: > + You'll find little hints like this one throughout the survey results that will point out extra features and details. + - + key: hints.units_switcher_hint + t: > + You can use the segmented control at the bottom of each block to switch between different units to get an alternate view of the same data. + - + key: hints.export_hint + t: > + The Data tab lets you view the raw data for any chart, view it as JSON, or get a GraphQL query you can run against our public API. + - + key: hints.completion_hint + t: > + Since all questions are optional, some of them got fewer responses than others. The completion indicator (◕) tells you exactly how many people answered any given question. + - + key: hints.tool_modal_hint + t: > + You can click on any technology name to get extra details and a more in-depth look at its related data. + - + key: hints.rankings_modes_hint + t: > + The Rankings chart can be toggled between satisfaction, interest, usage, and awareness to give you a fuller picture of a category's rankings. + - + key: hints.sharing_hint + t: > + Sharing this survey on Twitter, Facebook, or by email is scientifically proven to improve your coding performance by up to 15%. + - + key: hints.tshirt_hint + t: > + Another guaranteed scientific finding: buying our t-shirt will increase your programming skills by over 9000! + - + key: hints.variants_hint + t: > + Some charts feature additional tabs that offer complementary breakdowns of the same data, or related data. Make sure to check them out! + - + key: hints.share_hint + t: > + The Share tab makes it easy to share any chart, or even download it as an image. + - + key: hints.bracket_hint + t: > + The following chart provides the results of a tournament-style 8-player bracket in which respondents were tasked with picking the winner of each match-up until a single winner remained. + - + ########################################################################### + #Sponsor Chart + ########################################################################### + key: sections.sponsor_finish.title + t: Thanks + - + key: sponsor.sponsor_finish + t: > + Thanks for supporting the survey. Your avatar should appear next to the chart you picked within the next hour or so. If it doesn't, please [get in touch](mailto:chartsponsor@stateofjs.com). + - + key: sponsor.sponsored_by + t: > + **{name}** donated **${amount}** to sponsor this chart + - + key: sponsor.sponsor_button + t: Sponsor This Chart + - + key: sponsor.sponsor_chart.title + t: Sponsor Chart "{title}" + - + key: sponsor.sponsor_chart.description + t: > + Support this survey financially by donating $10 or more, and get your Twitter avatar featured next to a chart! + - + key: sponsor.chart_id + t: 'Chart ID: ' + - + key: sponsor.sponsor_this_chart + t: Sponsor This Chart (${baseAmount}+) + - + key: sponsor.how_it_works.title + t: How It Works + - + key: sponsor.how_it_works.description + t: > + 1. When you **click the "Sponsor This Chart" button**, you will be redirected to our partner [SendOwl](https://www.sendowl.com/)'s checkout page. + + 2. You can then **adjust the amount** you'd like to sponsor the survey for, starting at USD10. + + 3. Once you checkout, you will be able to **provide your Twitter username**. + + 4. You will see a **File Download** page, but you can safely ignore it. + + 5. The site will rebuild in the background and your username and donation will **appear next to the chart within the next hour**. + - + key: sponsor.faq.title + t: F.A.Q. + - + key: sponsor.faq.usage.title + t: What will my donation be used for? + - + key: sponsor.faq.usage.description + t: Your donation will help support survey maintainers, as well as help hire more contributors (illustrators, accessibilty and diversity experts, etc.). + - + key: sponsor.faq.public.title + t: Will my donation be public? + - + key: sponsor.faq.public.description + t: Yes. Your **Twitter username** as well as the **amount you donated** will be displayed publicly next to the chart. + - + #- key: sponsor.faq.donation_public.title + #t: Can I donate on somebody else's behalf? + #- key: sponsor.faq.donation_public.description + #t: You can enter a Twitter username other than your own, but that person will have the right to remove the donation if they request it. + key: sponsor.faq.refund.title + t: What's your refund policy? + - + key: sponsor.faq.refund.description + t: All donations are refundable within a 1-week period, minus transaction fees. + - + key: sponsor.faq.influence.title + t: Do donations influence the survey contents? + - + key: sponsor.faq.influence.description + t: Donations take place once the survey is already published, and donors to not have any influence on the contents of the survey. + - + key: sponsor.faq.feedback.title + t: Where can I leave feedback/ask questions? + - + key: sponsor.faq.feedback.description + t: You can do so [on GitHub](https://github.com/StateOfJS/Monorepo/issues/69) or [in our Discord](https://discord.gg/tuWRUWVyJs). From d414b0e65852d92ed86b26339d5ff150dd774aa8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:01 +0900 Subject: [PATCH 0188/1932] New translations state_of_css.yml (Portuguese) --- pt/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 pt/state_of_css.yml diff --git a/pt/state_of_css.yml b/pt/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/pt/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From de5859b2956c284b18a1da3aee04c98a8e146f96 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:02 +0900 Subject: [PATCH 0189/1932] New translations state_of_css.yml (Russian) --- ru/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 ru/state_of_css.yml diff --git a/ru/state_of_css.yml b/ru/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/ru/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From d39c7f9240d8490e06e7bca8e00278a8774adeb0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:03 +0900 Subject: [PATCH 0190/1932] New translations state_of_css_2020.yml (English) --- en/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 en/state_of_css_2020.yml diff --git a/en/state_of_css_2020.yml b/en/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/en/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 82e0756afa99802760dbe785d6fc1d1b4814d55b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:04 +0900 Subject: [PATCH 0191/1932] New translations state_of_css_2020.yml (Polish) --- pl/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 pl/state_of_css_2020.yml diff --git a/pl/state_of_css_2020.yml b/pl/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/pl/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From b542bd02b3cf51f26c37e50035efbc2b88036314 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:05 +0900 Subject: [PATCH 0192/1932] New translations state_of_css_2020.yml (Portuguese) --- pt/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 pt/state_of_css_2020.yml diff --git a/pt/state_of_css_2020.yml b/pt/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/pt/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 5bf3944545373d0f0cc00cb3182de9d6249d8f26 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:06 +0900 Subject: [PATCH 0193/1932] New translations state_of_css_2020.yml (Russian) --- ru/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 ru/state_of_css_2020.yml diff --git a/ru/state_of_css_2020.yml b/ru/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/ru/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 1b1d1621a0beaada492515ef817516836f46b02a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:06 +0900 Subject: [PATCH 0194/1932] New translations state_of_css_2020.yml (Serbian (Cyrillic)) --- sr/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 sr/state_of_css_2020.yml diff --git a/sr/state_of_css_2020.yml b/sr/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/sr/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 75316b9f1206019b821d44ffa167407042e90689 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:07 +0900 Subject: [PATCH 0195/1932] New translations state_of_css_2020.yml (Swedish) --- sv/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 sv/state_of_css_2020.yml diff --git a/sv/state_of_css_2020.yml b/sv/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/sv/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 1c47c4caf63ba0e9a543b139506ab70e6fbe45ee Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:08 +0900 Subject: [PATCH 0196/1932] New translations state_of_css_2020.yml (Turkish) --- tr/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 tr/state_of_css_2020.yml diff --git a/tr/state_of_css_2020.yml b/tr/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/tr/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From ed77f0ce86461d30e2d9e7627213c38d73ecb559 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:09 +0900 Subject: [PATCH 0197/1932] New translations state_of_css_2020.yml (Ukrainian) --- uk/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 uk/state_of_css_2020.yml diff --git a/uk/state_of_css_2020.yml b/uk/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/uk/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From f251d65309ff78b7e9e0626f9070f19662c90714 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:10 +0900 Subject: [PATCH 0198/1932] New translations state_of_css_2020.yml (Chinese Simplified) --- zh/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 zh/state_of_css_2020.yml diff --git a/zh/state_of_css_2020.yml b/zh/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/zh/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From d4867b823c0406297f4912caf3908f40f4304d0b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:11 +0900 Subject: [PATCH 0199/1932] New translations state_of_css_2020.yml (Vietnamese) --- vi/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 vi/state_of_css_2020.yml diff --git a/vi/state_of_css_2020.yml b/vi/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/vi/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 138188d21c1b0b095bd0dd2e0c8ed81daa7d70a2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:12 +0900 Subject: [PATCH 0200/1932] New translations state_of_css_2020.yml (Dutch) --- nl/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 nl/state_of_css_2020.yml diff --git a/nl/state_of_css_2020.yml b/nl/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/nl/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From e47fe9a67cbe4c3f4e951455aa26afe4eb25af32 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:14 +0900 Subject: [PATCH 0201/1932] New translations state_of_css_2021_results.yml (Romanian) --- ro/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 ro/state_of_css_2021_results.yml diff --git a/ro/state_of_css_2021_results.yml b/ro/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/ro/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 22f548450ab6e4462e6e5662b777a39fd2a1ae96 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:15 +0900 Subject: [PATCH 0202/1932] New translations state_of_css_2021_results.yml (French) --- fr/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 fr/state_of_css_2021_results.yml diff --git a/fr/state_of_css_2021_results.yml b/fr/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/fr/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 2adcaebf1c96ba4103447eb74addb3c64da3baed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:16 +0900 Subject: [PATCH 0203/1932] New translations state_of_css_2021_results.yml (Spanish) --- es/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 es/state_of_css_2021_results.yml diff --git a/es/state_of_css_2021_results.yml b/es/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/es/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From c6dae8285c3e2c07385fdb1d205d046f78e2f140 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:16 +0900 Subject: [PATCH 0204/1932] New translations state_of_css_2021_results.yml (Afrikaans) --- af/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 af/state_of_css_2021_results.yml diff --git a/af/state_of_css_2021_results.yml b/af/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/af/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 4dc9600efabc49350a157e5836a40b1b6b013cef Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:17 +0900 Subject: [PATCH 0205/1932] New translations state_of_css_2021_results.yml (Arabic) --- ar/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 ar/state_of_css_2021_results.yml diff --git a/ar/state_of_css_2021_results.yml b/ar/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/ar/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 98c168c9cc97f35f13b3d60e119e01a1728ce37d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:18 +0900 Subject: [PATCH 0206/1932] New translations state_of_css_2021_results.yml (Catalan) --- ca/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 ca/state_of_css_2021_results.yml diff --git a/ca/state_of_css_2021_results.yml b/ca/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/ca/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 8e940bbdb3b4ba4c8fb6d57d613e45c9971bf7d5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:19 +0900 Subject: [PATCH 0207/1932] New translations state_of_css_2021_results.yml (Czech) --- cs/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 cs/state_of_css_2021_results.yml diff --git a/cs/state_of_css_2021_results.yml b/cs/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/cs/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From c731fe722649bfc2857ef78b19ea8d938acb525f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:20 +0900 Subject: [PATCH 0208/1932] New translations state_of_css_2021_results.yml (Danish) --- da/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 da/state_of_css_2021_results.yml diff --git a/da/state_of_css_2021_results.yml b/da/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/da/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 67aa37eddc177f77c27492f5435c580552390c0c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:21 +0900 Subject: [PATCH 0209/1932] New translations state_of_css_2021_results.yml (German) --- de/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 de/state_of_css_2021_results.yml diff --git a/de/state_of_css_2021_results.yml b/de/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/de/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 58a6913fbead201733a52d552bb7a075fa32ecfc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:22 +0900 Subject: [PATCH 0210/1932] New translations state_of_css_2020.yml (Norwegian) --- no/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 no/state_of_css_2020.yml diff --git a/no/state_of_css_2020.yml b/no/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/no/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 3f3b8c0bc0b39aa6bb7290abee0b2db646caed9d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:22 +0900 Subject: [PATCH 0211/1932] New translations state_of_css_2020.yml (Korean) --- ko/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 ko/state_of_css_2020.yml diff --git a/ko/state_of_css_2020.yml b/ko/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/ko/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 1164e5cbfd122f6dc93f9a52902a99741768515b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:24 +0900 Subject: [PATCH 0212/1932] New translations state_of_css.yml (Serbian (Cyrillic)) --- sr/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 sr/state_of_css.yml diff --git a/sr/state_of_css.yml b/sr/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/sr/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From a320ea9209653ad79838eb2d3ee9ac6005bc7381 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:25 +0900 Subject: [PATCH 0213/1932] New translations state_of_css_2020.yml (Spanish) --- es/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 es/state_of_css_2020.yml diff --git a/es/state_of_css_2020.yml b/es/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/es/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 8b9c22d57ad1a57b9ffa72888321017b7ea734f0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:26 +0900 Subject: [PATCH 0214/1932] New translations state_of_css.yml (Swedish) --- sv/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 sv/state_of_css.yml diff --git a/sv/state_of_css.yml b/sv/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/sv/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From dbc03a7f855685e4befc6f3003de26bb78936603 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:27 +0900 Subject: [PATCH 0215/1932] New translations state_of_css.yml (Turkish) --- tr/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 tr/state_of_css.yml diff --git a/tr/state_of_css.yml b/tr/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/tr/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 08d2c518db40c7c379505af68f58f14bf8438892 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:28 +0900 Subject: [PATCH 0216/1932] New translations state_of_css.yml (Ukrainian) --- uk/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 uk/state_of_css.yml diff --git a/uk/state_of_css.yml b/uk/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/uk/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 74ce3fbabe81466c9c87e69409b6d4949dddedd3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:29 +0900 Subject: [PATCH 0217/1932] New translations state_of_css.yml (Chinese Simplified) --- zh/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 zh/state_of_css.yml diff --git a/zh/state_of_css.yml b/zh/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/zh/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 537512c73e988dc4acd91189d050ffcce970d6d8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:30 +0900 Subject: [PATCH 0218/1932] New translations state_of_css.yml (English) --- en/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 en/state_of_css.yml diff --git a/en/state_of_css.yml b/en/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/en/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 40889cbd8348796b8c398b14a2f0aeecfc4c2338 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:31 +0900 Subject: [PATCH 0219/1932] New translations state_of_css.yml (Vietnamese) --- vi/state_of_css.yml | 1021 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1021 insertions(+) create mode 100644 vi/state_of_css.yml diff --git a/vi/state_of_css.yml b/vi/state_of_css.yml new file mode 100644 index 00000000000..89fa59e1cfc --- /dev/null +++ b/vi/state_of_css.yml @@ -0,0 +1,1021 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2020 + t: > + CSS is evolving faster than ever. + + Flexbox, Grid, Multi-Column… To say nothing of whole new paradigms like CSS-in-JS. + + So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! + - + key: general.results.description + t: The annual survey about the latest trends in CSS. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.layout.title + t: Layout + - + key: sections.layout.description + t: How do you position elements on the screen? + - + key: sections.shapes_graphics.title + t: Shapes & Graphics + - + key: sections.shapes_graphics.description + t: Controlling the shape and display of elements. + - + key: sections.interactions.title + t: Interactions + - + key: sections.interactions.description + t: Controlling how the user interacts with the page. + - + key: sections.typography.title + t: Typography + - + key: sections.typography.description + t: Setting and laying out text. + - + key: sections.animations_transforms.title + t: Animations & Transforms + - + key: sections.animations_transforms.description + t: Animating and transforming elements. + - + key: sections.accessibility.title + t: Accessibility + - + key: sections.accessibility.description + t: Accessibility features and techniques. + - + key: sections.media_queries.title + t: Media Queries + - + key: sections.media_queries.description + t: Ways of adapting your site to the user's device or preferences. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other CSS features. + - + key: sections.units_selectors.title + t: Units & Selectors + - + key: sections.units_selectors.description + t: Test your knowledge of CSS units and selectors. + - + key: sections.pre_post_processors.title + t: Pre-/Post-processors + - + key: sections.pre_post_processors.description + t: Utilities that augment CSS. + - + key: sections.pre_post_processors_others.title + t: Other Pre-/Post-processors + - + key: sections.css_frameworks.title + t: CSS Frameworks + - + key: sections.css_frameworks.description + t: Libraries that give you pre-made components and styles. + - + key: sections.css_frameworks_others.title + t: Other CSS Frameworks + - + key: sections.css_methodologies.title + t: CSS Methodologies + - + key: sections.css_methodologies.description + t: Codified ways to write cleaner CSS. + - + key: sections.css_methodologies_others.title + t: Other CSS Methodologies. + - + key: sections.css_in_js.title + t: CSS-in-JS + - + key: sections.css_in_js.description + t: Libraries that help integrate CSS into JavaScript code. + - + key: sections.css_in_js_others.title + t: Other CSS-in-JS Libraries. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other CSS tools. + - + key: sections.environments.title + t: Environments + - + key: sections.environments.description + t: Which environments and accessibility concerns do you consider when writing CSS? + - + ########################################################################### + #Options + ########################################################################### + #CSS for print + key: options.css_for_print.0 + t: I (almost) never write print styles + - + key: options.css_for_print.0.short + t: Never + - + key: options.css_for_print.1 + t: I occasionally write print styles + - + key: options.css_for_print.1.short + t: Occasionally + - + key: options.css_for_print.2 + t: I write print styles as part of most projects + - + key: options.css_for_print.2.short + t: Often + - + key: options.css_for_print.3 + t: I focus mainly on CSS for print + - + key: options.css_for_print.3.short + t: Mainly + - + #CSS for email + key: options.css_for_email.0 + t: I (almost) never write CSS for email clients + - + key: options.css_for_email.0.short + t: Never + - + key: options.css_for_email.1 + t: I occasionally write CSS for email clients + - + key: options.css_for_email.1.short + t: Occasionally + - + key: options.css_for_email.2 + t: I write CSS for email clients as part of most projects + - + key: options.css_for_email.2.short + t: Often + - + key: options.css_for_email.3 + t: I focus mainly on CSS for email clients + - + key: options.css_for_email.3.short + t: Mainly + - + #what do you use CSS for? + key: options.what_do_you_use_css_for.marketing_sites + t: Marketing sites & landing pages + - + key: options.what_do_you_use_css_for.design_systems + t: Design systems + - + key: options.what_do_you_use_css_for.blogs + t: Blogs or other text-heavy sites + - + key: options.what_do_you_use_css_for.web_apps + t: Web apps + - + key: options.what_do_you_use_css_for.mobile_apps + t: Mobile apps + - + key: options.what_do_you_use_css_for.css_art + t: CSS art & illustrations + - + key: options.what_do_you_use_css_for.emails + t: Emails + - + key: options.what_do_you_use_css_for.printed_documents + t: Printed documents + - + #CSS pain points + key: options.css_pain_points.browser_interoperability + t: Browser Compatibility + - + key: options.css_pain_points.browser_interoperability.description + t: Differences between Chrome, Safari, Firefox, etc. + - + key: options.css_pain_points.interactions + t: Interactions + - + key: options.css_pain_points.interactions.description + t: Responding to user input or other events (scroll, hover, etc.). + - + key: options.css_pain_points.architecture + t: Architecture & Maintenance + - + key: options.css_pain_points.architecture.description + t: File organization, dead code elimination, refactoring, etc. + - + key: options.css_pain_points.layout_positioning + t: Layout & Positioning + - + key: options.css_pain_points.layout_positioning.description + t: Setting up layouts and making sure elements go where you want them to. + - + key: options.css_pain_points.scoping_specificity + t: Scoping & Specificity + - + key: options.css_pain_points.scoping_specificity.description + t: Dealing with the cascade, overriding styles, etc. + - + key: options.css_pain_points.responsive_design + t: Responsive Design + - + key: options.css_pain_points.responsive_design.description + t: Adapting layouts and designs for different form factors. + - + key: options.css_pain_points.form_elements_styling + t: Form Elements Styling + - + key: options.css_pain_points.form_elements_styling.description + t: Customizing how form elements look and behave. + - + key: options.css_pain_points.performance_issues + t: Performance Issues + - + key: options.css_pain_points.performance_issues.description + t: Dealing with scrolling jank, making animations smoother, etc. + - + #CSS missing features (same as features section) + key: options.currently_missing_from_css.nesting + t: Nesting + - + key: options.currently_missing_from_css.nesting.description + t: Being able to nest styles in native CSS. + - + key: options.currently_missing_from_css.parent_selector + t: Parent Selector + - + key: options.currently_missing_from_css.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: options.currently_missing_from_css.browser_support + t: Browser Support + - + key: options.currently_missing_from_css.browser_support.description + t: Better browser support for existing features. + - + key: options.currently_missing_from_css.mixins + t: Mixins + - + key: options.currently_missing_from_css.mixins.description + t: Group and reuse definitions dynamically. + - + key: options.currently_missing_from_css.color_functions + t: Color Functions + - + key: options.currently_missing_from_css.color_functions.description + t: Functions for manipulating color values. + - + key: options.currently_missing_from_css.container_queries + t: Container Queries + - + key: options.currently_missing_from_css.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: options.currently_missing_from_css.scoping + t: Scoping + - + key: options.currently_missing_from_css.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: options.currently_missing_from_css.subgrid + t: Subgrid + - + key: options.currently_missing_from_css.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Features + ########################################################################### + #layout + key: features.grid + t: CSS Grid + - + key: features.subgrid + t: Subgrid + - + key: features.regions + t: CSS Regions + - + key: features.flexbox + t: Flexbox + - + key: features.multi_column + t: CSS Multi-Column + - + key: features.writing_modes + t: CSS Writing Modes + - + key: features.exclusions + t: CSS Exclusions + - + key: features.position_sticky + t: 'position: sticky' + - + key: features.logical_properties + t: Logical Properties + - + key: features.logical_properties.description + t: margin-block-start, padding-inline-end, etc. + - + key: features.aspect_ratio + t: aspect-ratio + - + key: features.content_visibility + t: content-visibility + - + key: features.flexbox_gap + t: Gap property for flexbox + - + key: features.break_rules + t: Break rules + - + key: features.break_rules.description + t: break-inside, break-before, break-after + - + key: features.at_container + t: Container Queries + - + key: features.at_container.description + t: @container query + - + #shapes & graphics + key: features.shapes + t: CSS Shapes + - + key: features.object_fit + t: object-fit + - + key: features.clip_path + t: clip-path + - + key: features.masks + t: CSS Masks + - + key: features.blend_modes + t: Blend Modes + - + key: features.blend_modes.description + t: The mix-blend-mode property + - + key: features.filter_effects + t: CSS Filter Effects + - + key: features.backdrop_filter + t: backdrop-filter + - + key: features.intrinsic_sizing + t: Intrinsic Sizing + - + key: features.intrinsic_sizing.description + t: min-content, max-content, fit-content + - + key: features.repeating_linear_gradient + t: repeating-linear-gradient() + - + key: features.conic_gradient + t: conic-gradient() + - + key: features.color_function + t: color() + - + key: features.accent_color + t: accent-color + - + #interactions + key: features.scroll_snap + t: CSS Scroll Snap + - + key: features.overscroll_behavior + t: overscroll-behavior + - + key: features.overflow_anchor + t: overflow-anchor + - + key: features.touch_action + t: touch-action + - + key: features.pointer_events + t: pointer-events + - + key: features.scroll_timeline + t: scroll-timeline + - + #typography + key: features.web_fonts + t: Web fonts (@font-face) + - + key: features.variable_fonts + t: Variable fonts + - + key: features.line_breaking + t: Line breaking properties + - + key: features.line_breaking.description + t: overflow-wrap, word-break, line-break, hyphens + - + key: features.font_variant + t: font-variant-* + - + key: features.initial_letter + t: initial-letter + - + key: features.font_variant_numeric + t: font-variant-numeric + - + key: features.font_display + t: font-display + - + key: features.line_clamp + t: line-clamp + - + key: features.leading_trim + t: leading-trim + - + key: features.direction + t: direction + - + key: features.direction.description + t: Also includes dir HTML attribute. + - + #animations & transforms + key: features.transitions + t: CSS Transitions + - + key: features.transforms + t: CSS Transforms + - + key: features.animations + t: CSS Animations + - + key: features.perspective + t: perspective + - + #media queries/accessibility + key: features.feature_support_queries + t: Feature Support Queries (@supports) + - + key: features.prefers_reduced_motion + t: prefers-reduced-motion + - + key: features.prefers_color_scheme + t: prefers-color-scheme + - + key: features.color_gamut + t: color-gamut + - + key: features.prefers_reduced_data + t: prefers-reduced-data + - + key: features.tabindex + t: tabindex HTML attribute + - + key: features.tabindex.description + t: <div tabindex="0"> + - + key: features.color_contrast + t: color-contrast() + - + key: features.color_scheme + t: color-scheme + - + key: features.aria_attributes + t: ARIA HTML Attributes + - + key: features.aria_attributes.description + t: role, aria-label, etc. + - + #other features + key: features.variables + t: CSS Variables (Custom Properties) + - + key: features.containment + t: CSS Containment + - + key: features.will_change + t: will-change + - + key: features.calc + t: calc() + - + key: features.houdini + t: Houdini + - + key: features.comparison_functions + t: CSS Comparison Functions + - + key: features.comparison_functions.description + t: min(), max(), and clamp() + - + key: features.at_property + t: Houdini Custom Properties + - + key: features.at_property.description + t: @property + - + key: features.at_layer + t: @layer + - + key: features.content_visibility + t: content-visibility + - + key: features.marker + t: ::marker pseudo-element + - + #missing features (see also options) + key: features.nesting + t: Nesting + - + key: features.nesting.description + t: Being able to nest styles in native CSS. + - + key: features.parent_selector + t: Parent Selector + - + key: features.parent_selector.description + t: The ability to target a parent element based on its children. + - + key: features.browser_support + t: Browser Support + - + key: features.browser_support.description + t: Better browser support for existing features. + - + key: features.mixins + t: Mixins + - + key: features.mixins.description + t: Group and reuse definitions dynamically. + - + key: features.color_functions + t: Color Functions + - + key: features.color_functions.description + t: Functions for manipulating color values. + - + key: features.container_queries + t: Container Queries + - + key: features.container_queries.description + t: Being able to write styles based on the parent container's dimensions. + - + key: features.scoping + t: Scoping + - + key: features.scoping.description + t: The ability to be more specific about where your styles are applied. + - + key: features.subgrid + t: Subgrid + - + key: features.subgrid.description + t: Nesting deeper-level subgrids into a parent grid. + - + ########################################################################### + #Units & Selectors + ########################################################################### + key: features_others.units + t: Units + - + key: features_others.units.description + t: Which of these CSS units have you used? + - + key: options.units.px + t: px + - + key: options.units.pt + t: pt + - + key: options.units.percent + t: '%' + - + key: options.units.em + t: em + - + key: options.units.rem + t: rem + - + key: options.units.vh_vw + t: vh, vw + - + key: options.units.vmin_vmax + t: vmin, vmax + - + key: options.units.ch + t: ch + - + key: options.units.ex + t: ex + - + key: options.units.mm + t: mm + - + key: options.units.cm + t: cm + - + key: options.units.in + t: in + - + key: features_others.pseudo_elements + t: Pseudo Elements + - + key: features_others.pseudo_elements.description + t: Which of these CSS pseudo-elements have you used? + - + key: options.pseudo_elements.before + t: '::before' + - + key: options.pseudo_elements.after + t: '::after' + - + key: options.pseudo_elements.first_line + t: '::first-line' + - + key: options.pseudo_elements.first_letter + t: '::first-letter' + - + key: options.pseudo_elements.selection + t: '::selection' + - + key: options.pseudo_elements.placeholder + t: '::placeholder' + - + key: options.pseudo_elements.marker + t: '::marker' + - + key: options.pseudo_elements.backdrop + t: '::backdrop' + - + key: features_others.combinators + t: Combinators + - + key: features_others.combinators.description + t: Which of these combinations CSS selectors have you used? + - + key: options.combinators.descendant + t: div span (descendant) + - + key: options.combinators.child + t: div > span (child) + - + key: options.combinators.next_sibling + t: div + div (next sibling) + - + key: options.combinators.subsequent_sibling + t: div ~ div (subsequent sibling) + - + key: features_others.tree_document_structure + t: Tree / Document Structure + - + key: features_others.tree_document_structure.description + t: Which of these structure related CSS selectors have you used? + - + key: options.tree_document_structure.root + t: :root + - + key: options.tree_document_structure.empty + t: :empty + - + key: options.tree_document_structure.not + t: ':not()' + - + key: options.tree_document_structure.nth_child + t: ':nth-child()' + - + key: options.tree_document_structure.nth_last_child + t: ':nth-last-child()' + - + key: options.tree_document_structure.first_child + t: ':first-child' + - + key: options.tree_document_structure.last_child + t: ':last-child' + - + key: options.tree_document_structure.only_child + t: ':only-child' + - + key: options.tree_document_structure.nth_of_type + t: ':nth-of-type()' + - + key: options.tree_document_structure.nth_last_of_type + t: ':nth-last-of-type()' + - + key: options.tree_document_structure.first_of_type + t: ':first-of-type' + - + key: options.tree_document_structure.last_of_type + t: ':last-of-type' + - + key: options.tree_document_structure.only_of_type + t: ':only-of-type' + - + key: options.tree_document_structure.lang + t: ':lang()' + - + key: options.tree_document_structure.is + t: ':is()' + - + key: options.tree_document_structure.where + t: ':where()' + - + key: options.tree_document_structure.has + t: ':has()' + - + key: features_others.attributes + t: Attributes + - + key: features_others.attributes.description + t: Which of these CSS attributes selectors have you used? + - + key: options.attributes.presence + t: div[foo] (Presence) + - + key: options.attributes.equality + t: div[foo="bar"] (Equality) + - + key: options.attributes.starts_with + t: div[foo^="bar"] (Starts with) + - + key: options.attributes.ends_with + t: div[foo$="bar"] (Ends with) + - + key: options.attributes.contains_word + t: div[foo~="bar"] (Contains word) + - + key: options.attributes.contains_substring + t: div[foo*="bar"] (Contains substring) + - + key: features_others.links_urls + t: Links/URLs + - + key: features_others.links_urls.description + t: Which of these links & URLs related CSS selectors have you used? + - + key: options.links_urls.any_link + t: ':any-link' + - + key: options.links_urls.link_visited + t: ':link and :visited' + - + key: options.links_urls.local_link + t: ':local-link' + - + key: options.links_urls.target + t: :target + - + key: features_others.interaction + t: Interaction + - + key: features_others.interaction.description + t: Which of these interaction CSS selectors have you used? + - + key: options.interaction.hover + t: :hover + - + key: options.interaction.active + t: :active + - + key: options.interaction.focus + t: :focus + - + key: options.interaction.focus_within + t: ':focus-within' + - + key: options.interaction.focus_visible + t: ':focus-visible' + - + key: features_others.form_controls + t: Form Controls + - + key: features_others.form_controls.description + t: Which of these form related CSS selectors have you used? + - + key: options.form_controls.enabled_disabled + t: ':enabled and :disabled' + - + key: options.form_controls.read_only_write + t: ':read-only and :read-write' + - + key: options.form_controls.placeholder_shown + t: ':placeholder-shown' + - + key: options.form_controls.default + t: :default + - + key: options.form_controls.checked + t: :checked + - + key: options.form_controls.indeterminate + t: :indeterminate + - + key: options.form_controls.valid_invalid + t: ':valid and :invalid' + - + key: options.form_controls.user_invalid + t: ':user-invalid' + - + key: options.form_controls.in_out_range + t: ':in-range and :out-of-range' + - + key: options.form_controls.required_optional + t: ':required and :optional' + - + ########################################################################### + #Environments + ########################################################################### + key: environments.browsers + t: Browsers + - + key: environments.browsers.description + t: Which browsers do you test in? + - + key: environments.form_factors + t: Testing Environments + - + key: environments.form_factors.description + t: Which form factors or environments do you test on? + - + key: environments.accessibility_features + t: Accessibility Features + - + key: environments.accessibility_features.description + t: Which accessibility features do you usually implement? + - + key: environments.accessibility_features.others + t: Other Accessibility Features + - + key: environments.accessibility_features.others + t: Other accessibility features you usually implement + - + key: environments.css_for_print + t: CSS for Print + - + key: environments.css_for_print.description + t: Do you write print styles? + - + key: environments.css_for_email + t: CSS for Email Clients + - + key: environments.css_for_email.description + t: Do you write CSS for email clients? + - + key: environments.what_do_you_use_css_for + t: What do you mainly use CSS for? + - + key: environments.what_do_you_use_css_for.description + t: What kind of project do you usually use CSS for? + - + key: environments.what_do_you_use_css_for.others + t: Other kinds of projects + - + key: charts.axis_legends.css_for_print + t: Frequency + - + key: charts.axis_legends.css_for_email + t: Frequency + - + key: tools_others.tool_evaluation + t: Library Evaluation + - + key: tools_others.tool_evaluation.description + t: For each matchup, pick the factor you prioritize when evaluating a new library. + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.css_easy_to_learn + t: CSS is easy to learn + - + key: opinions.css_easy_to_learn.title + t: Learning Curve + - + key: opinions.css_evolving_slowly + t: CSS is evolving too slowly + - + key: opinions.css_evolving_slowly.title + t: Rate of Change + - + key: opinions.utility_classes_to_be_avoided + t: Utility (non-semantic) classes (.center, .large-text, etc.) should be avoided + - + key: opinions.utility_classes_to_be_avoided.title + t: Non-Semantic Classes + - + key: opinions.selector_nesting_to_be_avoided + t: Selector nesting (.foo .bar ul li {...}) should be avoided + - + key: opinions.selector_nesting_to_be_avoided.title + t: Selector Nesting + - + key: opinions.css_is_programming_language + t: CSS is a programming language + - + key: opinions.css_is_programming_language.title + t: Programming Language + - + key: opinions.enjoy_writing_css + t: I enjoy writing CSS + - + key: opinions.enjoy_writing_css.title + t: Enjoyment + - + #Browser interoperability question + key: opinions_others.browser_interoperability_features.others + t: Browser Incompatibilities + - + key: opinions_others.browser_interoperability_features.others.description + t: > + Are there any CSS features you have difficulties using because of differences between browsers? + - + #Pain Points + key: opinions.css_pain_points + t: CSS Pain Points + - + key: opinions.css_pain_points.description + t: For each matchup, pick the aspect of CSS you struggle with the most. + - + key: opinions_others.css_pain_points.others + t: Other CSS Pain Points + - + #Missing Features + key: opinions.currently_missing_from_css + t: What do you feel is currently missing from CSS? + - + key: opinions.currently_missing_from_css.description + t: For each matchup, pick the feature you'd most like to be able to use in CSS today. + - + key: opinions_others.currently_missing_from_css.others + t: Other Missing Features + - + key: opinions_others.currently_missing_from_css.others.note + t: > + These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). + - + key: opinions.sum_up_one_word_css + t: CSS in one word + - + key: opinions.sum_up_one_word_css.description + t: How would you sum up your opinion of CSS in one word? + - + key: happiness.pre_post_processors + t: How happy are you with the state of pre/post-processors? + - + key: happiness.css_in_js + t: How happy are you with the state of CSS-in-JS libraries? + - + key: happiness.css_frameworks + t: How happy are you with the state of CSS frameworks? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_css + t: How happy are you with the general state of CSS? + - + #pain points/currently missing (results) + key: css_pain_points.css_pain_points_wins + t: CSS Pain Points + - + key: css_pain_points.css_pain_points_wins.description + t: Which aspect of CSS do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: css_pain_points.css_pain_points_matchups + t: CSS Pain Points (Matchups) + - + key: css_pain_points.css_pain_points_matchups.description + t: Which aspect of CSS do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_css.currently_missing_from_css_wins + t: Features Missing From CSS + - + key: currently_missing_from_css.currently_missing_from_css_wins.description + t: Which feature would you most like to be able to use in CSS today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_css.currently_missing_from_css_matchups + t: Features Missing From CSS (Matchups) + - + key: currently_missing_from_css.currently_missing_from_css_matchups.description + t: Which feature would you most like to be able to use in CSS today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With CSS + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn CSS? From 1fe4cfd4283f5ec5cccfa16df42905c079434ead Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:33 +0900 Subject: [PATCH 0220/1932] New translations state_of_css_2020.yml (Romanian) --- ro/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 ro/state_of_css_2020.yml diff --git a/ro/state_of_css_2020.yml b/ro/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/ro/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From ab7ad7dc847b675d8301e560f718ebacc12ce70c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:34 +0900 Subject: [PATCH 0221/1932] New translations state_of_css_2020.yml (French) --- fr/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 fr/state_of_css_2020.yml diff --git a/fr/state_of_css_2020.yml b/fr/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/fr/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 188931c574eb21e54996b892331ef63ede38ed67 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:35 +0900 Subject: [PATCH 0222/1932] New translations state_of_css_2020.yml (Afrikaans) --- af/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 af/state_of_css_2020.yml diff --git a/af/state_of_css_2020.yml b/af/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/af/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From fe8c1c9bcec281e9da405f4ed16d7ea4fbc10070 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:36 +0900 Subject: [PATCH 0223/1932] New translations state_of_css_2020.yml (Japanese) --- ja/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 ja/state_of_css_2020.yml diff --git a/ja/state_of_css_2020.yml b/ja/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/ja/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From b9ecd802325053aa65df167e05d33c09c45fed17 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:37 +0900 Subject: [PATCH 0224/1932] New translations state_of_css_2020.yml (Arabic) --- ar/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 ar/state_of_css_2020.yml diff --git a/ar/state_of_css_2020.yml b/ar/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/ar/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 2cf0dbe6715bed11a2fd669faa47395cafb225f4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:38 +0900 Subject: [PATCH 0225/1932] New translations state_of_css_2020.yml (Catalan) --- ca/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 ca/state_of_css_2020.yml diff --git a/ca/state_of_css_2020.yml b/ca/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/ca/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 36c665798969f7058f1a8871242ba0b622d01610 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:38 +0900 Subject: [PATCH 0226/1932] New translations state_of_css_2020.yml (Czech) --- cs/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 cs/state_of_css_2020.yml diff --git a/cs/state_of_css_2020.yml b/cs/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/cs/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 443fc807916be65913ab27d7a5f33799654d09cc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:39 +0900 Subject: [PATCH 0227/1932] New translations state_of_css_2020.yml (Danish) --- da/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 da/state_of_css_2020.yml diff --git a/da/state_of_css_2020.yml b/da/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/da/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From f29b7ab9c4271a10d692a6189cb6845b65221e29 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:40 +0900 Subject: [PATCH 0228/1932] New translations state_of_css_2020.yml (German) --- de/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 de/state_of_css_2020.yml diff --git a/de/state_of_css_2020.yml b/de/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/de/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 8ab74c816c448ba7d32e1177e5519fb175616f28 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:41 +0900 Subject: [PATCH 0229/1932] New translations state_of_css_2020.yml (Greek) --- el/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 el/state_of_css_2020.yml diff --git a/el/state_of_css_2020.yml b/el/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/el/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From e04677fb74c3a4513b50af479ac3378980802c89 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:42 +0900 Subject: [PATCH 0230/1932] New translations state_of_css_2020.yml (Finnish) --- fi/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 fi/state_of_css_2020.yml diff --git a/fi/state_of_css_2020.yml b/fi/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/fi/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 9433407865448dd410d0dee1cfb3d05b462519ee Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:42 +0900 Subject: [PATCH 0231/1932] New translations state_of_css_2020.yml (Hebrew) --- he/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 he/state_of_css_2020.yml diff --git a/he/state_of_css_2020.yml b/he/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/he/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 2273e2c0481c2678ec11126349102e6232e6716f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:43 +0900 Subject: [PATCH 0232/1932] New translations state_of_css_2020.yml (Hungarian) --- hu/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 hu/state_of_css_2020.yml diff --git a/hu/state_of_css_2020.yml b/hu/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/hu/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From 1de05fc16c045b53ea519d8bc267bbd2cd0323fb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:44 +0900 Subject: [PATCH 0233/1932] New translations state_of_css_2020.yml (Italian) --- it/state_of_css_2020.yml | 277 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 it/state_of_css_2020.yml diff --git a/it/state_of_css_2020.yml b/it/state_of_css_2020.yml new file mode 100644 index 00000000000..6ac5b303b48 --- /dev/null +++ b/it/state_of_css_2020.yml @@ -0,0 +1,277 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Forget everything you know about CSS. Or at least, be ready to reconsider a lot of it. If like me you've been writing CSS for over a decade, CSS in 2020 looks nothing like what you were used to. + + Instead of breakpoints, we can now leverage CSS Grid to make dynamic, responsive layouts that adapt to any viewport size with fewer lines of code. Instead of relying on global stylesheets, CSS-in-JS lets us colocate our styles with our components to build themeable design systems. + + And most of all, Tailwind CSS has burst onto the scene and, through its use of utility-first CSS, forced us to reconsider the traditional dogma of semantic class names. + + Whether all this change makes you want to write a hyped-up blog post or an angry Twitter rant, we are here to present the data, highlight the trends, and hopefully guide you through another eventful year of CSS! + + ### Team + + The State of CSS Survey is created and maintained by: + + - [Sacha Greif](https://twitter.com/sachagreif): Design, writing, coding + - [Raphaël Benitte](https://twitter.com/benitteraphael): Data analysis, data visualizations + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + ### Other Links + + - [State of CSS Homepage](https://stateofcss.com) + - [State of JS](https://stateofjs.com) + + ### Thanks + + Thanks to all the people who helped us design the survey, including [Chen Hui-Jing](http://chenhuijing.com/), [Philip Jägenstedt](https://blog.foolip.org/), [Adam Argyle](https://nerdy.dev/), [Ahmad Shadeed](https://www.ishadeed.com/), [Robert Flack](https://github.com/flackr), [Dominic Nguyen](https://www.chromatic.com/), [Fantasai](http://fantasai.inkedblade.net/), and [Kilian Valkhof](https://kilianvalkhof.com/). + + Additional thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + ### Credits & Stuff + + The site is set in IBM Plex Mono. Questions? Feedback? [Get in touch!](mailto:hello@stateofjs.com) + + And now, let's see what CSS has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + A quick announcement before the survey results. Introducing our very own 🎈🎉👕 State of CSS T-shirt 👕🎉🎈! + + What makes this shirt truly special is that it's the only piece of clothing that also teaches you practical, real-world CSS techniques. + + So whether you're going to a conference, a job interview, or just work, this shirt will demonstrate your CSS mastery like no other garment can! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + The shirt features the State of CSS logo along with snippets of the actual CSS code used to create each shape. Who knows, you might learn a thing or two! + + We use a high-quality, super-soft tri-blend shirt with a slim fit. + This shirt sizes small, so if you prefer a looser fit we recommend ordering one size up from what you usually wear (I'm wearing an M in the photos). + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $24 + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **11,492** people in **102** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + CSS has seen a surge of new features in recent years, so as you'd expect adoption is + lagging a bit behind as the community takes its time to absorb new properties. + - + key: sections.units_selectors.description + t: | + We're willing to bet you'll find a few things you didn't know about in this section! + - + key: sections.technologies.description + t: | + The CSS ecosystem is going through a renewal of sorts, as older mainstays like Bootstrap + now have to accomodate newer entrants like Tailwind CSS. To say nothing of the whole CSS-in-JS + movement which, while it has yet to cross over to the CSS mainstream, is nonetheless quite dynamic. + - + key: sections.other_tools.description + t: | + No big surprises here, but it's worth highlighting the appearance of development-focused browsers + like Polypane and Sizzy, which go a step further than traditional devtools. + - + key: sections.environments.description + t: | + One of CSS's core strengths is its ability to adapt to different environment, yet for a variety + of reasons media like print and email remain unexplored by a majority of CSS developers. Might they + turn out to be the next frontier of CSS…? + - + key: sections.resources.description + t: | + The “other answers” results in this section highlight the richness and diversity of the CSS community, + and feature many outstanding blogs and podcasts which we are looking forward to officially adding + to the survey next year! + - + key: sections.opinions.description + t: | + These opinions paint a picture of a language getting more mature, but also more complex. And perhaps + –at least while we struggle to keep up with the pace of change– a little less enjoyable? + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + - + key: award.tool_usage_delta_award.comment + t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + - + key: award.tool_satisfaction_award.comment + t: PostCSS's **{value}** satisfaction ratio shows that you can't beat doing one thing really, really well. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules have generated the most interest among CSS developers this year. + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + If a JavaScript developer writes a line of CSS code, are they now a CSS developer? + + This programming *kōan* illustrates a clear trend in the web development world: as more and more CSS developers are tasked with learning JavaScript, so are JavaScript developers starting to realize there might be more to this whole CSS thing than just `font-weight: bold;`. + + So asking about “the State of CSS” is inherently a tricky proposition: depending on who you ask you might get completely different answers! And how do you know which one's right? + + Here's another kōan for you: the right answer is that there *is* no right answer. Each of the many tools, methodologies, frameworks, and libraries featured here has its place in the vast front-end ecosystem. + + Building a complex React app? Styled Components is a great option. Designing a static landing page? You can't go wrong with Sass! And even though Bootstrap has lost some of its original hype factor, you can't beat it when it comes to sheer number of themes and plugins. + + So while we keep an eye on the shiny new toys popping up on GitHub every week, let's not forget the tools, techniques, and most of all people who have carried the CSS torch up to now. We'll need everybody if we're to keep CSS moving forward into 2021 and beyond! + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.shadeed9.bio + t: Author of debuggingcss.com + - + key: picks.shadeed9.description + t: | + Container queries are a long-time awaited feature for us, + and I’m thrilled that the Chrome team is working on support for it natively! + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + The humble CSS box is more dynamic every year, and for me 2020 was about logical sides, instead of physical sides. Free internationally contextual content flow, spacing and shorthands? pls & ty + - + key: picks.sachagreif.bio + t: Creator of this survey + - + key: picks.sachagreif.description + t: | + With this blog post, Amelia Wattenberger didn't just go the extra mile, she ran a whole marathon! The animations and quiz will ensure you finally understand the CSS cascade. + - + key: picks.christianoliff.bio + t: Front-end developer for Trimble MAPS + - + key: picks.christianoliff.description + t: | + One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + `content-visibility` is making a huge difference in the performance of my web apps already, but at the same time I think it should be the job of browsers to optimize this, not devs. + - + key: picks.walterstephanie.bio + t: User Centered Designer & CSS Lover + - + key: picks.walterstephanie.description + t: | + A series of YouTube videos that explain all the new cool CSS features to build modern designs. + - + key: picks.piccalilli_.bio + t: Freelance designer & dev who runs piccalil.li + - + key: picks.piccalilli_.description + t: | + This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + - + key: picks.sarasoueidan.bio + t: Independent UI/design engineer + - + key: picks.sarasoueidan.description + t: | + My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + - + key: picks.5t3ph.bio + t: Software Engineer @ Microsoft + - + key: picks.5t3ph.description + t: | + In this conference talk, Manuel Matuzovic provides thoughtfully + crafted examples that are engaging, approachable, and actionable. + - + key: picks.hugogiraudel.bio + t: Non-binary accessibility & diversity advocate + - + key: picks.hugogiraudel.description + t: | + Fela is an amazing piece of software. + It’s pretty powerful, relatively easy to use and very performant + - + key: picks.foolip.bio + t: Software Engineer @ Google + - + key: picks.foolip.description + t: | + Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + notably bringing flex gap to WebKit, + which means that soon it will be available on all modern browsers. + - + key: picks.jina.bio + t: Design systems advocate and practitioner + - + key: picks.jina.description + t: | + The media query to reduce motion, which helps avoid + triggering dizziness and discomfort. From f57242578088821ef68bddc5f94c612277803f86 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:45 +0900 Subject: [PATCH 0234/1932] New translations state_of_css_2021_results.yml (Greek) --- el/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 el/state_of_css_2021_results.yml diff --git a/el/state_of_css_2021_results.yml b/el/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/el/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 59be67a68fc3cc8e6dd5aff0d5bd26712d07ec15 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:46 +0900 Subject: [PATCH 0235/1932] New translations state_of_css_2021_results.yml (Finnish) --- fi/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 fi/state_of_css_2021_results.yml diff --git a/fi/state_of_css_2021_results.yml b/fi/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/fi/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 9908cf4161e9e03cb6ce5fc8a9e39db6b8c80d4a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:46 +0900 Subject: [PATCH 0236/1932] New translations state_of_css_2021_survey.yml (Norwegian) --- no/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 no/state_of_css_2021_survey.yml diff --git a/no/state_of_css_2021_survey.yml b/no/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/no/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 23c56a0e36d63d2820ff7c318101cd5a66e00512 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:47 +0900 Subject: [PATCH 0237/1932] New translations state_of_css_2021_survey.yml (German) --- de/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 de/state_of_css_2021_survey.yml diff --git a/de/state_of_css_2021_survey.yml b/de/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/de/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 03a389993d1bd0a51e772399f7b610abc964d7ba Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:48 +0900 Subject: [PATCH 0238/1932] New translations state_of_css_2021_survey.yml (Greek) --- el/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 el/state_of_css_2021_survey.yml diff --git a/el/state_of_css_2021_survey.yml b/el/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/el/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From a04966cc1475f8ed69f440baf196da404c0204f4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:49 +0900 Subject: [PATCH 0239/1932] New translations state_of_css_2021_survey.yml (Finnish) --- fi/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 fi/state_of_css_2021_survey.yml diff --git a/fi/state_of_css_2021_survey.yml b/fi/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/fi/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 75029c1d51bb9ec3e2123a1c52346902c017b079 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:50 +0900 Subject: [PATCH 0240/1932] New translations state_of_css_2021_survey.yml (Hebrew) --- he/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 he/state_of_css_2021_survey.yml diff --git a/he/state_of_css_2021_survey.yml b/he/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/he/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 0f8c043a01cdf00b47dde29b59b87991dab55047 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:51 +0900 Subject: [PATCH 0241/1932] New translations state_of_css_2021_survey.yml (Hungarian) --- hu/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 hu/state_of_css_2021_survey.yml diff --git a/hu/state_of_css_2021_survey.yml b/hu/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/hu/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 358ff310c3d02bcda3073108e5d374299a114fbb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:52 +0900 Subject: [PATCH 0242/1932] New translations state_of_css_2021_survey.yml (Italian) --- it/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 it/state_of_css_2021_survey.yml diff --git a/it/state_of_css_2021_survey.yml b/it/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/it/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 93772217de65368c3d9e08d1858dd90996eb7be2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:53 +0900 Subject: [PATCH 0243/1932] New translations state_of_css_2021_survey.yml (Japanese) --- ja/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ja/state_of_css_2021_survey.yml diff --git a/ja/state_of_css_2021_survey.yml b/ja/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/ja/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 5eb76d0245fe2f72d52d2ced0fcbee0674d1ec42 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:54 +0900 Subject: [PATCH 0244/1932] New translations state_of_css_2021_survey.yml (Korean) --- ko/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ko/state_of_css_2021_survey.yml diff --git a/ko/state_of_css_2021_survey.yml b/ko/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/ko/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 9da0789cb72b6af6b9846d372da7a7a3590fcb0f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:55 +0900 Subject: [PATCH 0245/1932] New translations state_of_css_2021_survey.yml (Dutch) --- nl/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 nl/state_of_css_2021_survey.yml diff --git a/nl/state_of_css_2021_survey.yml b/nl/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/nl/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From e81d2e438df142ae215acf2bbad2a98c3220166b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:55 +0900 Subject: [PATCH 0246/1932] New translations state_of_css_2021_survey.yml (Polish) --- pl/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 pl/state_of_css_2021_survey.yml diff --git a/pl/state_of_css_2021_survey.yml b/pl/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/pl/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From cfae619fd0517ed2f7b78df87d414d04e57f4403 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:56 +0900 Subject: [PATCH 0247/1932] New translations state_of_css_2021_survey.yml (Czech) --- cs/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 cs/state_of_css_2021_survey.yml diff --git a/cs/state_of_css_2021_survey.yml b/cs/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/cs/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From cfa53d6e12b01fb5475e981a11b9ede83a06eb67 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:57 +0900 Subject: [PATCH 0248/1932] New translations state_of_css_2021_survey.yml (Portuguese) --- pt/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 pt/state_of_css_2021_survey.yml diff --git a/pt/state_of_css_2021_survey.yml b/pt/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/pt/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 24e84ce7a6fc5a1693e9ab5c1bc223fef936d8ad Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:58 +0900 Subject: [PATCH 0249/1932] New translations state_of_css_2021_survey.yml (Russian) --- ru/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ru/state_of_css_2021_survey.yml diff --git a/ru/state_of_css_2021_survey.yml b/ru/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/ru/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 2dee905e776ed16554b7dfa016bf34f21ba13f56 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:04:59 +0900 Subject: [PATCH 0250/1932] New translations state_of_css_2021_survey.yml (Serbian (Cyrillic)) --- sr/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 sr/state_of_css_2021_survey.yml diff --git a/sr/state_of_css_2021_survey.yml b/sr/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/sr/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From b9c600fb8538eae19c642637b73efa8734ba4f29 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:00 +0900 Subject: [PATCH 0251/1932] New translations state_of_css_2021_survey.yml (Swedish) --- sv/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 sv/state_of_css_2021_survey.yml diff --git a/sv/state_of_css_2021_survey.yml b/sv/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/sv/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From da9eb06298cecc3d66e8fd4313f1201a6444087c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:02 +0900 Subject: [PATCH 0252/1932] New translations state_of_css_2021_survey.yml (Turkish) --- tr/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 tr/state_of_css_2021_survey.yml diff --git a/tr/state_of_css_2021_survey.yml b/tr/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/tr/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 880fe7ea83b6435a1b3585d4122b6922d14c3775 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:03 +0900 Subject: [PATCH 0253/1932] New translations state_of_css_2021_survey.yml (Ukrainian) --- uk/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 uk/state_of_css_2021_survey.yml diff --git a/uk/state_of_css_2021_survey.yml b/uk/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/uk/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From cf2fd97f437545133e3815b2ede755e359e880ab Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:04 +0900 Subject: [PATCH 0254/1932] New translations state_of_css_2021_survey.yml (Chinese Simplified) --- zh/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 zh/state_of_css_2021_survey.yml diff --git a/zh/state_of_css_2021_survey.yml b/zh/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/zh/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 53121ae725ab69521801405ac42b627e0c127829 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:06 +0900 Subject: [PATCH 0255/1932] New translations state_of_css_2021_survey.yml (English) --- en/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 en/state_of_css_2021_survey.yml diff --git a/en/state_of_css_2021_survey.yml b/en/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/en/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From f98caa60d8052f4e0a636978005923eff776aed4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:07 +0900 Subject: [PATCH 0256/1932] New translations state_of_css_2021_survey.yml (Vietnamese) --- vi/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 vi/state_of_css_2021_survey.yml diff --git a/vi/state_of_css_2021_survey.yml b/vi/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/vi/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From d566275d3c2400dbf572a67507a6e7e8d0d5afce Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:07 +0900 Subject: [PATCH 0257/1932] New translations state_of_css_2021_survey.yml (Danish) --- da/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 da/state_of_css_2021_survey.yml diff --git a/da/state_of_css_2021_survey.yml b/da/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/da/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 961316b0878f4507fd29452fc77fbe7bba717472 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:08 +0900 Subject: [PATCH 0258/1932] New translations state_of_css_2021_survey.yml (Catalan) --- ca/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ca/state_of_css_2021_survey.yml diff --git a/ca/state_of_css_2021_survey.yml b/ca/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/ca/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 1c7127591063f8c310a290976cfb2d9ddc3f6483 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:09 +0900 Subject: [PATCH 0259/1932] New translations state_of_css_2021_results.yml (Hebrew) --- he/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 he/state_of_css_2021_results.yml diff --git a/he/state_of_css_2021_results.yml b/he/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/he/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 02320456cf2e787a83b16822a8c231c2829f7b4e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:10 +0900 Subject: [PATCH 0260/1932] New translations state_of_css_2021_results.yml (Swedish) --- sv/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 sv/state_of_css_2021_results.yml diff --git a/sv/state_of_css_2021_results.yml b/sv/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/sv/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 13c563978f8ebbec3fe177552af0fe65019f9cae Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:11 +0900 Subject: [PATCH 0261/1932] New translations state_of_css_2021_results.yml (Hungarian) --- hu/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 hu/state_of_css_2021_results.yml diff --git a/hu/state_of_css_2021_results.yml b/hu/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/hu/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 8ddf2b8ac08e4399d5f53531a5aa4e9945830a7c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:12 +0900 Subject: [PATCH 0262/1932] New translations state_of_css_2021_results.yml (Italian) --- it/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 it/state_of_css_2021_results.yml diff --git a/it/state_of_css_2021_results.yml b/it/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/it/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 6a7fa95e71d1f29e9de100186961f80979205361 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:13 +0900 Subject: [PATCH 0263/1932] New translations state_of_css_2021_results.yml (Japanese) --- ja/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 ja/state_of_css_2021_results.yml diff --git a/ja/state_of_css_2021_results.yml b/ja/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/ja/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From f04e3c5d0a58cc84bf4b6e92a8ce813eefb027f5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:14 +0900 Subject: [PATCH 0264/1932] New translations state_of_css_2021_results.yml (Korean) --- ko/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 ko/state_of_css_2021_results.yml diff --git a/ko/state_of_css_2021_results.yml b/ko/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/ko/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 9392e451801f7e78b45303abfaadf4c8751fb7b3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:15 +0900 Subject: [PATCH 0265/1932] New translations state_of_css_2021_results.yml (Dutch) --- nl/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 nl/state_of_css_2021_results.yml diff --git a/nl/state_of_css_2021_results.yml b/nl/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/nl/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 5690a6f14bd91d0c0356e6059168a7104b743429 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:16 +0900 Subject: [PATCH 0266/1932] New translations state_of_css_2021_results.yml (Norwegian) --- no/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 no/state_of_css_2021_results.yml diff --git a/no/state_of_css_2021_results.yml b/no/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/no/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From c7797b0f2de74651677806fa9b59d1a5765c15f1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:17 +0900 Subject: [PATCH 0267/1932] New translations state_of_css_2021_results.yml (Polish) --- pl/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 pl/state_of_css_2021_results.yml diff --git a/pl/state_of_css_2021_results.yml b/pl/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/pl/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 57ff35e5587f3d941c3949e576cfe8076a6ab060 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:18 +0900 Subject: [PATCH 0268/1932] New translations state_of_css_2021_results.yml (Portuguese) --- pt/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 pt/state_of_css_2021_results.yml diff --git a/pt/state_of_css_2021_results.yml b/pt/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/pt/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From fd396c38b9221bd802f24ab7f615e94466c1940a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:19 +0900 Subject: [PATCH 0269/1932] New translations state_of_css_2021_results.yml (Russian) --- ru/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 ru/state_of_css_2021_results.yml diff --git a/ru/state_of_css_2021_results.yml b/ru/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/ru/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 2ae254aa726d6264be182b4285cfe90e5ac9cb45 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:20 +0900 Subject: [PATCH 0270/1932] New translations state_of_css_2021_results.yml (Serbian (Cyrillic)) --- sr/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 sr/state_of_css_2021_results.yml diff --git a/sr/state_of_css_2021_results.yml b/sr/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/sr/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 5d15bbcedc05e854f9e2c5f59ac45067c022b6a2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:21 +0900 Subject: [PATCH 0271/1932] New translations state_of_css_2021_results.yml (Turkish) --- tr/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 tr/state_of_css_2021_results.yml diff --git a/tr/state_of_css_2021_results.yml b/tr/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/tr/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 4e1458f3c66a52dba05199b52b9c2d3fc1571e81 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:21 +0900 Subject: [PATCH 0272/1932] New translations state_of_css_2021_survey.yml (Arabic) --- ar/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ar/state_of_css_2021_survey.yml diff --git a/ar/state_of_css_2021_survey.yml b/ar/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/ar/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From d1b6904d5ffaa3299487964af1d856bc5aa5d842 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:22 +0900 Subject: [PATCH 0273/1932] New translations state_of_css_2021_results.yml (Ukrainian) --- uk/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 uk/state_of_css_2021_results.yml diff --git a/uk/state_of_css_2021_results.yml b/uk/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/uk/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 0e24c9eeb88ca44e72ceb429957a9db425a7598d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:23 +0900 Subject: [PATCH 0274/1932] New translations state_of_css_2021_results.yml (Chinese Simplified) --- zh/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 zh/state_of_css_2021_results.yml diff --git a/zh/state_of_css_2021_results.yml b/zh/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/zh/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 44053902d99fad48bbee088c63d82fee4dc098cb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:25 +0900 Subject: [PATCH 0275/1932] New translations state_of_css_2021_results.yml (English) --- en/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 en/state_of_css_2021_results.yml diff --git a/en/state_of_css_2021_results.yml b/en/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/en/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 4166814bc8463248ede5fd09be87bb161594f622 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:26 +0900 Subject: [PATCH 0276/1932] New translations state_of_css_2021_results.yml (Vietnamese) --- vi/state_of_css_2021_results.yml | 457 +++++++++++++++++++++++++++++++ 1 file changed, 457 insertions(+) create mode 100644 vi/state_of_css_2021_results.yml diff --git a/vi/state_of_css_2021_results.yml b/vi/state_of_css_2021_results.yml new file mode 100644 index 00000000000..3585174fc1b --- /dev/null +++ b/vi/state_of_css_2021_results.yml @@ -0,0 +1,457 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + Do woodworkers have to learn a new, better way to saw a board every couple years? Do painters feel like frauds for still using oil paint? Or is it just us front-end developers who get to experience this constant state of change? + + With container queries and more just around the corner, things are definitely moving fast. And since we need to keep up as well, we took the time to give these survey results a couple new power-ups of their own! + + What this means in practice is that we can now cross-reference two datapoints, such as yearly salaries by experience level; or gender by country. You'll see some of these breakdowns included throughout the results, but we encourage you to explore the data further using [our API](https://api.stateofjs.com/) or by [downloading our data](https://www.kaggle.com/sachag/state-of-css). Let us know if you end up making your own data visualizations! + + And now, let's see what CSS has been up to this year! + + *Note: We've had to push back the 2021 [State of JavaScript](http://stateofjs.com/) survey to January 2022 for lack of time. See you after the holidays!* + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of CSS T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for CSS at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **8,714** developers throughout the world, and in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + CSS's dynamism shows no sign of stopping, as developers make an effort to adopt the current + crop of new features while looking forward to even more innovation in the next few years. + - + key: sections.technologies.description + t: | + With nearly 50% of respondents happily using one or more CSS-in-JS library, it's safe to say that + the category has managed to carve out its niche. Maybe the two sides of the front-end world are + not so far apart after all? + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites is fine, but this year we decided to go one step further + and actually feature the people who make up the CSS community themselves! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with CSS! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.layout + aliasFor: sections.layout.title + - + key: options.features_categories.shapes_graphics + aliasFor: sections.shapes_graphics.title + - + key: options.features_categories.interactions + aliasFor: sections.interactions.title + - + key: options.features_categories.typography + aliasFor: sections.typography.title + - + key: options.features_categories.animations_transforms + aliasFor: sections.animations_transforms.title + - + key: options.features_categories.accessibility + aliasFor: sections.accessibility.title + - + key: options.features_categories.media_queries + aliasFor: sections.media_queries.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, CSS comparison functions are becoming a key part of every CSS developer's toolkit. + - + #- key: award.tool_usage_delta_award.comment + #t: No other tool comes even close to Tailwind CSS's dramatic **{value}** progression over the last year. + key: award.tool_satisfaction_award.comment + t: PostCSS takes the top spot once again with a **{value}** satisfaction ratio. + - + key: award.tool_interest_award.comment + t: With a **{value}** ratio, CSS Modules again generated the most interest among CSS developers this year. + - + #- key: award.most_write_ins_award.comment + #t: Many questions also accepted write-in answers, and with **{value}** mentions PhpStorm was the most popular item overall. + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + The way you write CSS is about to change forever + + For many years now, many innovations in writing styles for the web have happened elsewhere: in preprocessors, JavaScript frameworks, or compilers. To be sure, CSS itself has also received some welcome improvements like [aspect-ratio](https://developer.mozilla.org/en-US/docs/Web/CSS/aspect-ratio) or [custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/--*). Yet we still reach for libraries and other helpers on a daily basis. + + But there's a change coming. The core CSS language is getting shaken up and renewed, and we're right at the forefront of accelerated evolution. + + [Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries) will bring in an entirely new era of responsive design, and [Cascade Layers](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer) will make our use of frameworks, theming and managing complex codebases significantly easier. + + When we look a little further ahead, we can also see the [@when/else conditional](https://css-tricks.com/proposal-for-css-when/) coming up, which will let us combine media, container and supports queries into a single at-rule. + + And fingers crossed, 2022 is the year we finally see some movement on native CSS nesting. Those of us that work with tools like Sass and PostCSS already couldn't imagine another way of working. + + All of this together means that 2022 is likely to be a year where the way you write CSS is going to fundamentally change. It's an incredibly exciting period, and we look forward to all the amazing implementations in the year to come. + - + key: conclusion.bio + t: Web developer and creator of Polypane + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the CSS community to share their “pick of the year” + - + key: picks.georgedoescode.name + t: The CSS Paint API + - + key: picks.georgedoescode.bio + t: Developer, writer, and generative artist. + - + key: picks.georgedoescode.description + t: | + The Paint API allows us to create images programmatically, + to use in our CSS. It unlocks a whole world of creativity, + and I am very excited about it! + - + key: picks.cassidoo.name + t: Lynn Fisher + - + key: picks.cassidoo.bio + t: Developer advocate, educator, and startup advisor. + - + key: picks.cassidoo.description + t: | + I'd love to pick Lynn Fisher. She's consistently surprised + and delighted the CSS community with her creative projects and experiments, + and I love how much folks can learn from her! + - + key: picks.joshwcomeau.name + t: Amelia Wattenberger + - + key: picks.joshwcomeau.bio + t: Software developer and creator of [CSS for JavaScript Developers](https://css-for-js.dev/). + - + key: picks.joshwcomeau.description + t: | + Amelia is creating some of the most amazing + interactive blog posts about CSS and JS. + Check out this post about how percentages work in CSS! + - + key: picks.kevinjpowell.name + t: Stephanie Eckles + - + key: picks.kevinjpowell.bio + t: CSS Evangelist + - + key: picks.kevinjpowell.description + t: | + I'm constantly blown away by Stephanie's continued initiatives + to help share her knowledge of modern CSS techniques, + as well as her contagious enthusiasm for CSS. + - + key: picks.mmatuzo.name + t: aspect-ratio + - + key: picks.mmatuzo.bio + t: Front-end developer from Vienna, and creator of [htmhell.dev](https://htmhell.dev). + - + key: picks.mmatuzo.description + t: | + All major browsers shipped support for aspect-ratio in 2021. + At first I underestimated it, but there are so many + situations where this property comes in handy. + - + key: picks.lauragift_.name + t: Kevin Powell + - + key: picks.lauragift_.bio + t: Frontend Developer and Content Creator + - + key: picks.lauragift_.description + t: | + Kevin creates CSS content on YouTube and I really enjoy watching his videos a lot. + He does a really good job teaching CSS concepts in a way that's easy and fun + to understand. + - + key: picks.ericwbailey.name + t: Miriam Suzanne + - + key: picks.ericwbailey.bio + t: 'Inclusive Design and \#a11y advocate.' + - + key: picks.ericwbailey.description + t: | + CSS is about to go from good to great. + Miriam's work on Container Queries and Cascade Layers is going + to revolutionize how CSS is written. + - + key: picks.samuelkraft.name + t: Vanilla Extract + - + key: picks.samuelkraft.bio + t: Frontend & design + - + key: picks.samuelkraft.description + t: | + Lately I've loved working with Vanilla Extract, it's like CSS Modules but + fully typed with a magical developer experience. + - + key: picks.sachagreif.name + t: Open Props + - + key: picks.sachagreif.bio + t: State of JS and State of CSS creator + - + key: picks.sachagreif.description + t: | + It's really cool to see the feedback loop between new CSS features and new + projects taking advantage of them! And I think Adam Argyle's Open Props + is a great use of Custom Properties (CSS variables). + - + key: picks.shadeed9.name + t: Container Queries + - + key: picks.shadeed9.bio + t: Author of [Debugging CSS](https://debuggingcss.com/), Writing at [ishadeed.com](http://ishadeed.com) + - + key: picks.shadeed9.description + t: | + CSS container queries again! We got the chance to play with them in a browser. + Thanks to Miriam Suzanne for moving this forward! + I can't wait to use them without a flag. + - + #- key: picks.georgedoescode.name + #t: + #- key: picks.georgedoescode.bio + #t: + #- key: picks.georgedoescode.description + #t: | + key: picks.argyleink.name + t: CSS Noise + - + key: picks.argyleink.bio + t: CSS at Google + - + key: picks.argyleink.description + t: | + CSS generated texture and randomness makes for unique and + interesting paint jobs in your design. + Noise tools have made the technique accessible. + - + key: picks.walterstephanie.name + t: Miriam Suzanne + - + key: picks.walterstephanie.bio + t: UX Researcher and CSS lover + - + key: picks.walterstephanie.description + t: | + Miriam is an artist and an activist who creates software and art that celebrate the queer complexity of human experience. She's a CSS expert, and is doing an amazing job on the specifications for CSS Container Queries. + - + key: picks.michebarks.name + t: '“Building a Color Scheme” by Adam Argyle' + - + key: picks.michebarks.bio + t: Senior Front End Developer + - + key: picks.michebarks.description + t: | + I love this article because although custom properties have been around for a while now, it really takes them to a different level and showcases their power. I hope it makes some people think of them in a different way, as more than simple variables. + - + #- key: picks.christianoliff.bio + #t: Front-end developer for Trimble MAPS + #- key: picks.christianoliff.description + #t: | + #One thing I've really started using and appreciating this year though is Purge CSS- an awesome tool for removing unused CSS. It can greatly reduce the size of your CSS, and its fast and easy to use. + key: picks.kilianvalkhof.name + t: prefers-reduced-data + - + key: picks.kilianvalkhof.bio + t: Web developer and creator of Polypane + - + key: picks.kilianvalkhof.description + t: | + We need more devs to ask browsers about this feature, and to realize how big a difference it can make. With 64% of respondents not knowing it though, we have work to do! + - + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.piccalilli_.bio + #t: Freelance designer & dev who runs piccalil.li + #- key: picks.piccalilli_.description + #t: | + #This blog is an absolute gold mine of CSS knowledge. Michelle is a CSS legend and every post or tutorial they write is heaped with useful content. + #- key: picks.sarasoueidan.bio + #t: Independent UI/design engineer + #- key: picks.sarasoueidan.description + #t: | + #My pick is a person, namely Rachel Andrew. She taught CSS Grid to a whole generation of developers. + #- key: picks.5t3ph.bio + #t: Software Engineer @ Microsoft + #- key: picks.5t3ph.description + #t: | + #In this conference talk, Manuel Matuzovic provides thoughtfully + #crafted examples that are engaging, approachable, and actionable. + #- key: picks.hugogiraudel.bio + #t: Non-binary accessibility & diversity advocate + #- key: picks.hugogiraudel.description + #t: | + #Fela is an amazing piece of software. + #It’s pretty powerful, relatively easy to use and very performant + #- key: picks.foolip.bio + #t: Software Engineer @ Google + #- key: picks.foolip.description + #t: | + #Sergio has recently fixed lots of Flexbox in WebKit and even some in Chromium, + #notably bringing flex gap to WebKit, + #which means that soon it will be available on all modern browsers. + #- key: picks.jina.bio + #t: Design systems advocate and practitioner + #- key: picks.jina.description + #t: | + #The media query to reduce motion, which helps avoid + #triggering dizziness and discomfort. + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of CSS survey ran from October 5 to November 2 2021, and collected 8714 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + + This year's logo and t-shirt were designed and animated by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of JavaScript](https://stateofjs.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/StateOfCSS-2020/issues/8). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: this year, we reached out to 23 organizations representing BIPOC and LGBTQ developers in the hopes of partnering up. While very few of them replied, we will keep looking for ways to reach out beyond our current audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the survey. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From fc3b4cf3fd82dc09bb1fa03646076d2384d6cf54 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:28 +0900 Subject: [PATCH 0277/1932] New translations state_of_css_2021_survey.yml (Romanian) --- ro/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ro/state_of_css_2021_survey.yml diff --git a/ro/state_of_css_2021_survey.yml b/ro/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/ro/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From d89dfc3e49d804b245486e0a4d3f6fcbb0d39972 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:29 +0900 Subject: [PATCH 0278/1932] New translations state_of_css_2021_survey.yml (French) --- fr/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 fr/state_of_css_2021_survey.yml diff --git a/fr/state_of_css_2021_survey.yml b/fr/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/fr/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 167990a52029e31c3f44986ec23aa2674abed2ed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:31 +0900 Subject: [PATCH 0279/1932] New translations state_of_css_2021_survey.yml (Spanish) --- es/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 es/state_of_css_2021_survey.yml diff --git a/es/state_of_css_2021_survey.yml b/es/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/es/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 35df2a98673266eeea9d81ac924ae74915470f25 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:32 +0900 Subject: [PATCH 0280/1932] New translations state_of_css_2021_survey.yml (Afrikaans) --- af/state_of_css_2021_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 af/state_of_css_2021_survey.yml diff --git a/af/state_of_css_2021_survey.yml b/af/state_of_css_2021_survey.yml new file mode 100644 index 00000000000..1c22a120867 --- /dev/null +++ b/af/state_of_css_2021_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: css +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_css2021 + t: > + Hey CSS, what have you been up to lately? Oh really, `@container`? Oh and intrinsic sizing? And `@property` too?! Wow, you've been busy! + + Even though the pandemic kept on making everybody's lives harder throughout 2021, somehow dedicated contributors around the world managed to keep CSS moving forward. And so once more it's time to survey the CSS ecosystem and figure out where this is all going. And maybe learn about a few new things while you're at it! From 9b56987e677d50a822f218b089d61c02de564489 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:35 +0900 Subject: [PATCH 0281/1932] New translations state_of_js.yml (Romanian) --- ro/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 ro/state_of_js.yml diff --git a/ro/state_of_js.yml b/ro/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/ro/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From ad4fe710a071718636007fd234140793822b8de7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:37 +0900 Subject: [PATCH 0282/1932] New translations state_of_js_2020.yml (Danish) --- da/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 da/state_of_js_2020.yml diff --git a/da/state_of_js_2020.yml b/da/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/da/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 1a77fb02dbf78c102e4cdf9a2d5f4ee774495ccd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:38 +0900 Subject: [PATCH 0283/1932] New translations state_of_js.yml (Vietnamese) --- vi/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 vi/state_of_js.yml diff --git a/vi/state_of_js.yml b/vi/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/vi/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 243a55e184a69316b31e20e23cc7a456e0f8ffb9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:40 +0900 Subject: [PATCH 0284/1932] New translations state_of_js.yml (Portuguese, Brazilian) --- pt/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 pt/state_of_js.yml diff --git a/pt/state_of_js.yml b/pt/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/pt/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 15602b6b4af72b6c4396acf85deb00c33ffb0787 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:41 +0900 Subject: [PATCH 0285/1932] New translations state_of_js_2020.yml (Romanian) --- ro/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 ro/state_of_js_2020.yml diff --git a/ro/state_of_js_2020.yml b/ro/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/ro/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From bee35a4f7ba9291ca933944f8b1d6a3a13a65bb2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:43 +0900 Subject: [PATCH 0286/1932] New translations state_of_js_2020.yml (French) --- fr/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 fr/state_of_js_2020.yml diff --git a/fr/state_of_js_2020.yml b/fr/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/fr/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 471caa291d2421aa3023acc79399f2b9008fc82a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:45 +0900 Subject: [PATCH 0287/1932] New translations state_of_js_2020.yml (Spanish) --- es/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 es/state_of_js_2020.yml diff --git a/es/state_of_js_2020.yml b/es/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/es/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 2aed5b327af55c9b6067eb3a4b87ba0b64ab72d8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:46 +0900 Subject: [PATCH 0288/1932] New translations state_of_js_2020.yml (Afrikaans) --- af/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 af/state_of_js_2020.yml diff --git a/af/state_of_js_2020.yml b/af/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/af/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From bd87c3117e24d28f04d1c3fec1ecfde58bfd2528 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:48 +0900 Subject: [PATCH 0289/1932] New translations state_of_js_2020.yml (Arabic) --- ar/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 ar/state_of_js_2020.yml diff --git a/ar/state_of_js_2020.yml b/ar/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/ar/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 95254b0cae41d95d1374020688b788b1142ed2dd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:49 +0900 Subject: [PATCH 0290/1932] New translations state_of_js_2020.yml (Catalan) --- ca/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 ca/state_of_js_2020.yml diff --git a/ca/state_of_js_2020.yml b/ca/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/ca/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From e693141ae7ab55eba635d6f417fcb9c317554252 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:50 +0900 Subject: [PATCH 0291/1932] New translations state_of_js_2020.yml (Czech) --- cs/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 cs/state_of_js_2020.yml diff --git a/cs/state_of_js_2020.yml b/cs/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/cs/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 2d8a4f4f182c5af4f8e7f2fa9324cda37b1c912a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:51 +0900 Subject: [PATCH 0292/1932] New translations state_of_js_2020.yml (German) --- de/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 de/state_of_js_2020.yml diff --git a/de/state_of_js_2020.yml b/de/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/de/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 0d5a24be13b0a96630e1562777ee746119104db0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:52 +0900 Subject: [PATCH 0293/1932] New translations state_of_js.yml (Chinese Traditional) --- zh/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 zh/state_of_js.yml diff --git a/zh/state_of_js.yml b/zh/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/zh/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 1d9d0f9e9b95fa607875bb609dd5d8cf37e1842a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:53 +0900 Subject: [PATCH 0294/1932] New translations state_of_js_2020.yml (Greek) --- el/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 el/state_of_js_2020.yml diff --git a/el/state_of_js_2020.yml b/el/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/el/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 9416fa84bdf94094572a6d9f629cb862207fa538 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:55 +0900 Subject: [PATCH 0295/1932] New translations state_of_js_2020.yml (Finnish) --- fi/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 fi/state_of_js_2020.yml diff --git a/fi/state_of_js_2020.yml b/fi/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/fi/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 0b284a040b340c4e31dd6191a14f464968f7c507 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:55 +0900 Subject: [PATCH 0296/1932] New translations state_of_js_2020.yml (Hebrew) --- he/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 he/state_of_js_2020.yml diff --git a/he/state_of_js_2020.yml b/he/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/he/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 49f60cff21e29378f7d0c521b0973f765cd2d737 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:56 +0900 Subject: [PATCH 0297/1932] New translations state_of_js_2020.yml (Hungarian) --- hu/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 hu/state_of_js_2020.yml diff --git a/hu/state_of_js_2020.yml b/hu/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/hu/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 3dc22f161be76e3ff5c1788a1def6e9bef3f218d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:57 +0900 Subject: [PATCH 0298/1932] New translations state_of_js_2020.yml (Italian) --- it/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 it/state_of_js_2020.yml diff --git a/it/state_of_js_2020.yml b/it/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/it/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 77a7a1d26507164919465f7fc1a4f5c8d18c4a71 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:58 +0900 Subject: [PATCH 0299/1932] New translations state_of_js_2020.yml (Japanese) --- ja/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 ja/state_of_js_2020.yml diff --git a/ja/state_of_js_2020.yml b/ja/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/ja/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From d7d035e89e595f49812934b0bcd7cd7545cff85c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:05:59 +0900 Subject: [PATCH 0300/1932] New translations state_of_js_2020.yml (Korean) --- ko/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 ko/state_of_js_2020.yml diff --git a/ko/state_of_js_2020.yml b/ko/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/ko/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 2a47c92905d73fcb7849dd130e4c71494bf54a3b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:00 +0900 Subject: [PATCH 0301/1932] New translations state_of_js_2020.yml (Dutch) --- nl/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 nl/state_of_js_2020.yml diff --git a/nl/state_of_js_2020.yml b/nl/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/nl/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 8965242e2e4d202c70aca81212685d61024a4b50 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:01 +0900 Subject: [PATCH 0302/1932] New translations state_of_js_2020.yml (Norwegian) --- no/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 no/state_of_js_2020.yml diff --git a/no/state_of_js_2020.yml b/no/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/no/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 85194c332298e7b76d537398032e2c66cb4ff9c1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:02 +0900 Subject: [PATCH 0303/1932] New translations state_of_js_2020.yml (Polish) --- pl/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 pl/state_of_js_2020.yml diff --git a/pl/state_of_js_2020.yml b/pl/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/pl/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From ee900f817780fdebb9925af376e73e88a7727ddd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:03 +0900 Subject: [PATCH 0304/1932] New translations state_of_js.yml (English) --- en/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 en/state_of_js.yml diff --git a/en/state_of_js.yml b/en/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/en/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 386f62ac2131f89d6ef46405e5d853d7fd741c74 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:05 +0900 Subject: [PATCH 0305/1932] New translations state_of_js.yml (French) --- fr/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 fr/state_of_js.yml diff --git a/fr/state_of_js.yml b/fr/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/fr/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From daac17e1788d7a1c1cdaeaf702726bd6adc99116 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:06 +0900 Subject: [PATCH 0306/1932] New translations state_of_js.yml (Hungarian) --- hu/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 hu/state_of_js.yml diff --git a/hu/state_of_js.yml b/hu/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/hu/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From d05d1c05d8e72274cdc2cc88d4ab94c3666fbe11 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:07 +0900 Subject: [PATCH 0307/1932] New translations state_of_js.yml (Spanish) --- es/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 es/state_of_js.yml diff --git a/es/state_of_js.yml b/es/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/es/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From ca6f9d135a56e03b8773f6de0218ff2182bdb72a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:08 +0900 Subject: [PATCH 0308/1932] New translations state_of_js.yml (Afrikaans) --- af/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 af/state_of_js.yml diff --git a/af/state_of_js.yml b/af/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/af/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From b45d4c1320bd079dd7b72b49a16d32a4d8bce4df Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:09 +0900 Subject: [PATCH 0309/1932] New translations state_of_js.yml (Arabic) --- ar/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 ar/state_of_js.yml diff --git a/ar/state_of_js.yml b/ar/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/ar/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 1728f2856c52985bd559fd12f6d0475593fcbbd9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:10 +0900 Subject: [PATCH 0310/1932] New translations state_of_js.yml (Catalan) --- ca/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 ca/state_of_js.yml diff --git a/ca/state_of_js.yml b/ca/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/ca/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From b10cf6150419e534c5c08bdea5f8510034316ddd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:11 +0900 Subject: [PATCH 0311/1932] New translations state_of_js.yml (Czech) --- cs/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 cs/state_of_js.yml diff --git a/cs/state_of_js.yml b/cs/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/cs/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 5bfa4a97dfb337fb9feefd3b9a34951ebfd1ac7e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:12 +0900 Subject: [PATCH 0312/1932] New translations state_of_js.yml (Danish) --- da/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 da/state_of_js.yml diff --git a/da/state_of_js.yml b/da/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/da/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From ba066738889e24549b55693aa7c3a4827a92a810 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:13 +0900 Subject: [PATCH 0313/1932] New translations state_of_js.yml (German) --- de/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 de/state_of_js.yml diff --git a/de/state_of_js.yml b/de/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/de/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From cc7b9a2addb2b1e12b3b2a4ab69b107b9e040cb5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:14 +0900 Subject: [PATCH 0314/1932] New translations state_of_js.yml (Greek) --- el/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 el/state_of_js.yml diff --git a/el/state_of_js.yml b/el/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/el/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 73e04a3314f2d6a12d63ac023b0c7fca496317d9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:15 +0900 Subject: [PATCH 0315/1932] New translations state_of_js.yml (Finnish) --- fi/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 fi/state_of_js.yml diff --git a/fi/state_of_js.yml b/fi/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/fi/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From b8c4b80b08f88dec24c3867e61631149bca653d2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:16 +0900 Subject: [PATCH 0316/1932] New translations state_of_js.yml (Hebrew) --- he/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 he/state_of_js.yml diff --git a/he/state_of_js.yml b/he/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/he/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From e0ae3a574f4803238657858383efe27dff1d0dfb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:16 +0900 Subject: [PATCH 0317/1932] New translations state_of_js.yml (Italian) --- it/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 it/state_of_js.yml diff --git a/it/state_of_js.yml b/it/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/it/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 1f79d75174c3fe1f59752d5b369bcfb205141fab Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:17 +0900 Subject: [PATCH 0318/1932] New translations state_of_js.yml (Ukrainian) --- uk/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 uk/state_of_js.yml diff --git a/uk/state_of_js.yml b/uk/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/uk/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From d7a6b7267b421013ad3eb73925f7c24f7fcc3bd9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:18 +0900 Subject: [PATCH 0319/1932] New translations state_of_js.yml (Japanese) --- ja/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 ja/state_of_js.yml diff --git a/ja/state_of_js.yml b/ja/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/ja/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 5e5527603b34a8df24218899cb88967fb4f46e43 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:19 +0900 Subject: [PATCH 0320/1932] New translations state_of_js.yml (Korean) --- ko/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 ko/state_of_js.yml diff --git a/ko/state_of_js.yml b/ko/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/ko/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 90934868a5fe39ddf1e5b718923c122269b84142 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:20 +0900 Subject: [PATCH 0321/1932] New translations state_of_js.yml (Dutch) --- nl/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 nl/state_of_js.yml diff --git a/nl/state_of_js.yml b/nl/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/nl/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From c5a237e9231aa564fe53c474f93fa619be6a6a12 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:21 +0900 Subject: [PATCH 0322/1932] New translations state_of_js.yml (Norwegian) --- no/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 no/state_of_js.yml diff --git a/no/state_of_js.yml b/no/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/no/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 86a4e44fc01aecf2839dac1425789dcc272048f0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:22 +0900 Subject: [PATCH 0323/1932] New translations state_of_js.yml (Polish) --- pl/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 pl/state_of_js.yml diff --git a/pl/state_of_js.yml b/pl/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/pl/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 160106674ae4de514d5c371fc445e620a3f83f5b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:24 +0900 Subject: [PATCH 0324/1932] New translations state_of_js.yml (Russian) --- ru/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 ru/state_of_js.yml diff --git a/ru/state_of_js.yml b/ru/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/ru/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 7f3a7641b47b20b5bf52b667560edfa40aacece7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:25 +0900 Subject: [PATCH 0325/1932] New translations state_of_js.yml (Serbian (Cyrillic)) --- sr/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 sr/state_of_js.yml diff --git a/sr/state_of_js.yml b/sr/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/sr/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 39004a2a0aa5414feeebe4dbf1684493efc62bef Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:25 +0900 Subject: [PATCH 0326/1932] New translations state_of_js.yml (Swedish) --- sv/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 sv/state_of_js.yml diff --git a/sv/state_of_js.yml b/sv/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/sv/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From b9f15ad05468003e4632a868b9d911ce691b69a8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:26 +0900 Subject: [PATCH 0327/1932] New translations state_of_js.yml (Turkish) --- tr/state_of_js.yml | 589 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 589 insertions(+) create mode 100644 tr/state_of_js.yml diff --git a/tr/state_of_js.yml b/tr/state_of_js.yml new file mode 100644 index 00000000000..2ecff184581 --- /dev/null +++ b/tr/state_of_js.yml @@ -0,0 +1,589 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2019 + t: > + The JavaScript world could use a bit of classification. + + Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. + + Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + ########################################################################### + #Sections + ########################################################################### + key: sections.syntax.title + t: Syntax + - + key: sections.syntax.description + t: The grammar of JavaScript. + - + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of JavaScript. + - + key: sections.data_structures.title + t: Data Structures + - + key: sections.data_structures.description + t: How you store and manipulate data. + - + key: sections.browser_apis.title + t: Browser APIs + - + key: sections.browser_apis.description + t: The features provided by the browser. + - + key: sections.other_features.title + t: Other Features + - + key: sections.other_features.description + t: Other technologies and patterns + - + key: sections.patterns.title + t: Patterns + - + key: sections.patterns.description + t: How you prefer writing code + - + key: sections.javascript_flavors.title + t: JavaScript Flavors + - + key: sections.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: sections.front_end_frameworks.title + t: Front-end Frameworks + - + key: sections.front_end_frameworks.description + t: Front-end frameworks and libraries + - + key: sections.datalayer.title + t: Data Layer + - + key: sections.datalayer.description + t: Loading and managing data in your app + - + key: sections.back_end_frameworks.title + t: Back-end Frameworks + - + key: sections.back_end_frameworks.description + t: JavaScript on the server + - + key: sections.testing.title + t: Testing + - + key: sections.testing.description + t: Tools for testing your code + - + key: sections.mobile_desktop.title + t: Mobile & Desktop + - + key: sections.mobile_desktop.description + t: JavaScript for mobile devices and desktop apps + - + key: sections.build_tools.title + t: Build Tools + - + key: sections.build_tools.description + t: Compiling & bundling code + - + key: sections.monorepo_tools.title + t: Monorepo Tools + - + key: sections.monorepo_tools.description + t: Tools used to manage JavaScript monorepos. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other JavaScript tools + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + ########################################################################### + #Options + ########################################################################### + #JS pain points + #- key: options.js_pain_points.browser_interoperability + #t: Browser Compatibility + #- key: options.js_pain_points.browser_interoperability.description + #t: Differences between Chrome, Safari, Firefox, etc. + #- key: options.js_pain_points.animations + #t: Animations + #- key: options.js_pain_points.animations.description + #t: Managing animations, transitions, etc. using JavaScript. + #- key: options.js_pain_points.form_handling + #t: Form Handling + #- key: options.js_pain_points.form_handling.description + #t: Creating forms, managing their state and errors, and saving their data. + key: options.js_pain_points.state_management + t: State Management + - + key: options.js_pain_points.state_management.description + t: Managing global data state in complex applications. + - + #- key: options.js_pain_points.performance_issues + #t: Performance Issues + #- key: options.js_pain_points.performance_issues.description + #t: Bundle sizes, slow loading, and other performance issues. + key: options.js_pain_points.managing_dependencies + t: Managing Dependencies + - + key: options.js_pain_points.managing_dependencies.description + t: Managing dependencies, package versions and bundle sizes. + - + key: options.js_pain_points.architecture + t: Code Architecture + - + key: options.js_pain_points.architecture.description + t: Organizing and maintaining your codebase. + - + key: options.js_pain_points.finding_packages + t: Finding Packages + - + key: options.js_pain_points.finding_packages.description + t: Finding and evaluating JavaScript packages. + - + key: options.js_pain_points.writing_modules + t: Writing Modules + - + key: options.js_pain_points.writing_modules.description + t: Writing JavaScript modules and publishing them as packages. + - + key: options.js_pain_points.debugging + t: Debugging + - + key: options.js_pain_points.debugging.description + t: Identifying and solving issues with your code. + - + key: options.js_pain_points.async_code + t: Async Code + - + key: options.js_pain_points.async_code.description + t: Handling asynchronous functions. + - + key: options.js_pain_points.modules_management + t: Modules Management + - + key: options.js_pain_points.modules_management.description + t: Writing and importing modules. + - + key: options.js_pain_points.date_management + t: Date Management + - + key: options.js_pain_points.date_management.description + t: Handling and manipulating dates and times. + - + #- key: options.js_pain_points.xxx + #t: + #- key: options.js_pain_points.xxx.description + #t: + #JS missing features + key: options.currently_missing_from_js.static_typing + t: Static Typing + - + key: options.currently_missing_from_js.static_typing.description + t: Native types (similar to what TypeScript offers). + - + key: options.currently_missing_from_js.standard_library + t: Standard Library + - + key: options.currently_missing_from_js.standard_library.description + t: A standard library of common utilities + - + key: options.currently_missing_from_js.pattern_matching + t: Pattern Matching + - + key: options.currently_missing_from_js.pattern_matching.description + t: A new `match` keyword for pattern-matching objects. + - + key: options.currently_missing_from_js.pipe_operator + t: Pipe Operator + - + key: options.currently_missing_from_js.pipe_operator.description + t: A new `|>` operator for passing the result of one function to another. + - + key: options.currently_missing_from_js.decorators + t: Decorators + - + key: options.currently_missing_from_js.decorators.description + t: Decorators used to metaprogram and add functionality to a value. + - + key: options.currently_missing_from_js.immutable_data_structures + t: Immutable Data Structures + - + key: options.currently_missing_from_js.immutable_data_structures.description + t: New deeply immutable data structures such as `Record` and `Tuple`. + - + key: options.currently_missing_from_js.better_date_management + t: Better Date Management + - + key: options.currently_missing_from_js.better_date_management.description + t: A new `Temporal` object for working with dates and times. + - + key: options.currently_missing_from_js.observable + t: Observable + - + key: options.currently_missing_from_js.observable.description + t: A new `Observable`` type used to model push-based data sources. + - + #- key: options.currently_missing_from_js.xxx + #t: + #- key: options.currently_missing_from_js.xxx.description + #t: + ########################################################################### + #Features + ########################################################################### + #syntax + key: features.destructuring + t: Destructuring + - + key: features.destructuring.description + t: 'Example: `const { foo } = bar`' + - + key: features.spread_operator + t: Spread operator + - + key: features.spread_operator.description + t: 'Example: `[...array1, ...array2]`' + - + key: features.arrow_functions + t: Arrow Functions + - + key: features.arrow_functions.description + t: 'Example: `const foo = () => {}`' + - + key: features.nullish_coalescing + t: Nullish Coalescing + - + key: features.nullish_coalescing.description + t: > + Example: `const foo = 0 ?? 42` + - + key: features.optional_chaining + t: Optional Chaining + - + key: features.optional_chaining.description + t: > + Example: `const dogName = adventurer.dog?.name` + - + key: features.private_fields + t: Private Fields + - + key: features.private_fields.description + t: > + Example: `class ClassWithPrivateField { #privateField }` #privateField }` + - + #language + key: features.proxies + t: Proxies + - + key: features.async_await + t: Async/Await + - + key: features.promises + t: Promises + - + key: features.decorators + t: Decorators + - + key: features.decorators.description + t: > + In its simplest form, a decorator is simply a way of wrapping one piece of code with another — literally “decorating” it. + - + key: features.dynamic_import + t: Dynamic Import + - + key: features.dynamic_import.description + t: > + Example: await import('/modules/my-module.js') + - + key: features.promise_all_settled + t: Promise.allSettled() + - + key: features.big_int + t: BigInt + - + key: features.numeric_separators + t: Numeric Separators + - + key: features.string_replace_all + t: String.prototype.replaceAll() + - + key: features.string_match_all + t: String.prototype.matchAll() + - + key: features.logical_assignment + t: Logical Assignment + - + key: features.promise_any + t: Promise.any() + - + key: features.array_at + t: Array.prototype.at() + - + key: features.top_level_await + t: Top-Level Await + - + key: features.intl + t: Intl + - + key: features.custom_elements + t: Custom Elements + - + key: features.shadow_dom + t: Shadow DOM + - + key: features.page_visibility + t: Page Visibility API + - + key: features.broadcast_channel + t: Broadcast Channel API + - + key: features.geolocation + t: Geolocation API + - + key: features.file_system_access + t: File System Access API + - + key: features.web_share + t: Web Share API + - + key: features.webxr + t: WebXR + - + #data structures + key: features.maps + t: Maps + - + key: features.sets + t: Sets + - + key: features.typed_arrays + t: Typed Arrays + - + key: array_prototype_flat + t: Array.prototype.flat + - + #browser apis + key: features.service_workers + t: Service Workers + - + key: features.local_storage + t: LocalStorage + - + key: features.i18n + t: i18n + - + key: features.web_components + t: Web Components + - + key: features.web_audio + t: Web Audio API + - + key: features.webgl + t: WebGL + - + key: features.web_animations + t: Web Animations API + - + key: features.webrtc + t: WebRTC + - + key: features.web_speech + t: Web Speech API + - + key: features.webvr + t: WebVR + - + key: features.websocket + t: Websocket + - + key: features.fetch + t: Fetch API + - + #other features + key: features.pwa + t: Progressive Web Apps (PWA) + - + key: features.wasm + t: WebAssembly (WASM) + - + #patterns + key: patterns.object_oriented_programming + t: Object-Oriented Programming + - + key: features.functional_programming + t: Functional Programming + - + key: features.reactive_programming + t: Reactive Programming + - + #upcoming features + #- key: features.static_typing + #t: Static Typing + #- key: features.standard_library + #t: Standard Library + #- key: features.pattern_matching + #t: Pattern Matching + #- key: features.pipe_operator + #t: Pipe Operator + #- key: features.immutable_data_structures + #t: Immutable Data Structures + ########################################################################### + #Tools + ########################################################################### + key: tools.angular.description + t: > + Note that this question only targets [Angular](https://angular.io/) experience, and specifically does *not* apply to the deprecated [AngularJS](https://angularjs.org/). + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.runtimes + t: JavaScript Runtimes + - + key: tools_others.runtimes.description + t: Which engines/runtimes/execution environments do you regularly use? + - + key: tools_others.runtimes.others + t: Other Runtimes + - + key: tools_others.runtimes.others.description + t: Other answers (freeform field). + - + key: tools_others.package_registries + t: Package Registries + - + key: tools_others.package_registries.description + t: Which package registries do you regularly fetch packages from? + - + key: tools_others.package_registries.others + t: Other Package Registries + - + key: tools_others.package_registries.others.description + t: Other answers (freeform field). + - + key: tools_others.form_factors + aliasFor: environments.form_factors + - + key: tools_others.form_factors.description + aliasFor: environments.form_factors.description + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.js_moving_in_right_direction + t: JavaScript is moving in the right direction + - + key: opinions.building_js_apps_overly_complex + t: Building JavaScript apps is overly complex right now + - + key: opinions.js_over_used_online + t: JavaScript is over-used online + - + key: opinions.enjoy_building_js_apps + t: I enjoy building JavaScript apps + - + key: opinions.would_like_js_to_be_main_lang + t: I would like JavaScript to be my main programming language + - + key: opinions.js_ecosystem_changing_to_fast + t: The JavaScript ecosystem is changing too fast + - + key: opinions_others.missing_from_js.others + t: What do you feel is currently missing from JavaScript? + - + key: opinions_others.missing_from_js.others.description + t: Features you'd like to see in JavaScript one day. + - + key: happiness.front_end_frameworks + t: How happy are you with the state of front end frameworks? + - + key: happiness.back_end_frameworks + t: How happy are you with the state of back end frameworks? + - + key: happiness.testing + t: How happy are you with the state of testing tools? + - + key: happiness.mobile_desktop + t: How happy are you with the state of mobile & desktop frameworks? + - + key: happiness.build_tools + t: How happy are you with the state of build tools? + - + key: happiness.monorepo_tools + t: How happy are you with the state of monorepo tools? + - + key: happiness.state_of_the_web + t: How happy are you with the general state of web technologies? + - + key: happiness.state_of_js + t: How happy are you with the general state of JavaScript? + - + #Pain Points + key: opinions.js_pain_points + t: JavaScript Pain Points + - + key: opinions.js_pain_points.description + t: For each matchup, pick the aspect of JavaScript you struggle with the most. + - + key: opinions_others.js_pain_points.others + t: Other JavaScript Pain Points + - + #Missing Features + key: opinions.currently_missing_from_js + t: What do you feel is currently missing from JavaScript? + - + key: opinions.currently_missing_from_js.description + t: For each matchup, pick the feature you'd most like to be able to use in JavaScript today. + - + key: opinions_others.currently_missing_from_js.others + t: Other Missing Features + - + #pain points/currently missing (results) + key: js_pain_points.js_pain_points_wins + t: JavaScript Pain Points + - + key: js_pain_points.js_pain_points_wins.description + t: Which aspect of JavaScript do you struggle with the most? Results are ranked by number of tournament rounds won. + - + key: js_pain_points.js_pain_points_matchups + t: JavaScript Pain Points (Matchups) + - + key: js_pain_points.js_pain_points_matchups.description + t: Which aspect of JavaScript do you struggle with the most? Percentage of rounds won by left-hand item against top-side item. + - + key: currently_missing_from_js.currently_missing_from_js_wins + t: Features Missing From JavaScript + - + key: currently_missing_from_js.currently_missing_from_js_wins.description + t: Which feature would you most like to be able to use in JavaScript today? Results are ranked by number of tournament rounds won. + - + key: currently_missing_from_js.currently_missing_from_js_matchups + t: Features Missing From JavaScript (Matchups) + - + key: currently_missing_from_js.currently_missing_from_js_matchups.description + t: Which feature would you most like to be able to use in JavaScript today? Percentage of rounds won by left-hand item against top-side item. + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With JavaScript + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn JavaScript? From 74e768fb7e0a0009710342183003da9eb8ab1f3d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:27 +0900 Subject: [PATCH 0328/1932] New translations state_of_js_2020.yml (Portuguese) --- pt/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 pt/state_of_js_2020.yml diff --git a/pt/state_of_js_2020.yml b/pt/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/pt/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 3cb96d97eb6a433fd5ba564c9cd31c6467d2dcbc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:28 +0900 Subject: [PATCH 0329/1932] New translations state_of_js_2020.yml (Russian) --- ru/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 ru/state_of_js_2020.yml diff --git a/ru/state_of_js_2020.yml b/ru/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/ru/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From a00b3f64c70071b37c23125b2babb3e4bf320009 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:29 +0900 Subject: [PATCH 0330/1932] New translations state_of_js_2020_survey.yml (English) --- en/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 en/state_of_js_2020_survey.yml diff --git a/en/state_of_js_2020_survey.yml b/en/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/en/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 121f93a474b3eb77a6409c84ff4a57bdffdec6b0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:30 +0900 Subject: [PATCH 0331/1932] New translations state_of_js_2020_survey.yml (Polish) --- pl/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 pl/state_of_js_2020_survey.yml diff --git a/pl/state_of_js_2020_survey.yml b/pl/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/pl/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 0c35b4a432e607fae9bfd5f65e3a440f5e5a5731 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:30 +0900 Subject: [PATCH 0332/1932] New translations state_of_js_2020_survey.yml (Portuguese) --- pt/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 pt/state_of_js_2020_survey.yml diff --git a/pt/state_of_js_2020_survey.yml b/pt/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/pt/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 07cb9eac9514ef9f6d8c3e673949a85a2962716e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:31 +0900 Subject: [PATCH 0333/1932] New translations state_of_js_2020_survey.yml (Russian) --- ru/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ru/state_of_js_2020_survey.yml diff --git a/ru/state_of_js_2020_survey.yml b/ru/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/ru/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 932f306c25c8b87f44471904af0f1cf0298792d2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:32 +0900 Subject: [PATCH 0334/1932] New translations state_of_js_2020_survey.yml (Serbian (Cyrillic)) --- sr/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 sr/state_of_js_2020_survey.yml diff --git a/sr/state_of_js_2020_survey.yml b/sr/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/sr/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From bc74c1c2b4ed2b2894ca2fb97c68ae557502fee7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:33 +0900 Subject: [PATCH 0335/1932] New translations state_of_js_2020_survey.yml (Swedish) --- sv/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 sv/state_of_js_2020_survey.yml diff --git a/sv/state_of_js_2020_survey.yml b/sv/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/sv/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 277bbbc6394446e413ab33c5bd23e9382abcf79b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:34 +0900 Subject: [PATCH 0336/1932] New translations state_of_js_2020_survey.yml (Turkish) --- tr/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 tr/state_of_js_2020_survey.yml diff --git a/tr/state_of_js_2020_survey.yml b/tr/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/tr/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 354de514e2801c62ea2c623277ce3ee00776fe26 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:35 +0900 Subject: [PATCH 0337/1932] New translations state_of_js_2020_survey.yml (Ukrainian) --- uk/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 uk/state_of_js_2020_survey.yml diff --git a/uk/state_of_js_2020_survey.yml b/uk/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/uk/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 81291b34bf2678a5a2c66fc01de148c3d24382e9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:36 +0900 Subject: [PATCH 0338/1932] New translations state_of_js_2020_survey.yml (Chinese Simplified) --- zh/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 zh/state_of_js_2020_survey.yml diff --git a/zh/state_of_js_2020_survey.yml b/zh/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/zh/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From e0c911485ce21b5610488dd28a86166551240445 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:37 +0900 Subject: [PATCH 0339/1932] New translations state_of_js_2020_survey.yml (Vietnamese) --- vi/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 vi/state_of_js_2020_survey.yml diff --git a/vi/state_of_js_2020_survey.yml b/vi/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/vi/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 4f6866019a82ee62d16fd2e6b1db197aacdbac99 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:38 +0900 Subject: [PATCH 0340/1932] New translations state_of_js_2020_survey.yml (Dutch) --- nl/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 nl/state_of_js_2020_survey.yml diff --git a/nl/state_of_js_2020_survey.yml b/nl/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/nl/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From aca53fcd3aedb56acb1ac828d55cc34614db62bd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:40 +0900 Subject: [PATCH 0341/1932] New translations state_of_js_2021_results.yml (Romanian) --- ro/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 ro/state_of_js_2021_results.yml diff --git a/ro/state_of_js_2021_results.yml b/ro/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/ro/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 4f982f519cd89cfebaa67a08fe72e9adc99af681 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:41 +0900 Subject: [PATCH 0342/1932] New translations state_of_js_2021_results.yml (French) --- fr/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 fr/state_of_js_2021_results.yml diff --git a/fr/state_of_js_2021_results.yml b/fr/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/fr/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 5424294c36ecce3974a84f55322dded577265245 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:41 +0900 Subject: [PATCH 0343/1932] New translations state_of_js_2021_results.yml (Spanish) --- es/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 es/state_of_js_2021_results.yml diff --git a/es/state_of_js_2021_results.yml b/es/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/es/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From fb71d5b746ba49a7d6e6f05ecb3f07295037753b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:42 +0900 Subject: [PATCH 0344/1932] New translations state_of_js_2021_results.yml (Afrikaans) --- af/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 af/state_of_js_2021_results.yml diff --git a/af/state_of_js_2021_results.yml b/af/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/af/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 3412dbb55da954f75b03ffb76f6bb1b252134610 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:43 +0900 Subject: [PATCH 0345/1932] New translations state_of_js_2021_results.yml (Arabic) --- ar/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 ar/state_of_js_2021_results.yml diff --git a/ar/state_of_js_2021_results.yml b/ar/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/ar/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From aaef813ac98c2b16fdd02d3d4813161ee3ea4fe8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:44 +0900 Subject: [PATCH 0346/1932] New translations state_of_js_2021_results.yml (Catalan) --- ca/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 ca/state_of_js_2021_results.yml diff --git a/ca/state_of_js_2021_results.yml b/ca/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/ca/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 85e93696ae0917df3cce36c6df3d5444df40e9c4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:45 +0900 Subject: [PATCH 0347/1932] New translations state_of_js_2021_results.yml (Czech) --- cs/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 cs/state_of_js_2021_results.yml diff --git a/cs/state_of_js_2021_results.yml b/cs/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/cs/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 7855abf9196a7830bf9da1982a39eac750dab886 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:46 +0900 Subject: [PATCH 0348/1932] New translations state_of_js_2021_results.yml (Danish) --- da/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 da/state_of_js_2021_results.yml diff --git a/da/state_of_js_2021_results.yml b/da/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/da/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 60ef9ac65828379016dbadc2c19a7476889add05 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:47 +0900 Subject: [PATCH 0349/1932] New translations state_of_js_2021_results.yml (German) --- de/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 de/state_of_js_2021_results.yml diff --git a/de/state_of_js_2021_results.yml b/de/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/de/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 4db3e9b0cf6c6deb929ccb1390c66f1bb3cd45e4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:48 +0900 Subject: [PATCH 0350/1932] New translations state_of_js_2020_survey.yml (Norwegian) --- no/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 no/state_of_js_2020_survey.yml diff --git a/no/state_of_js_2020_survey.yml b/no/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/no/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From a26986ef34758a40bccd3b25b201f1a1e0f9d1a5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:49 +0900 Subject: [PATCH 0351/1932] New translations state_of_js_2020_survey.yml (Korean) --- ko/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ko/state_of_js_2020_survey.yml diff --git a/ko/state_of_js_2020_survey.yml b/ko/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/ko/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 5523c81737c16cb03c1462c2687cbc5293644d60 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:50 +0900 Subject: [PATCH 0352/1932] New translations state_of_js_2020.yml (Serbian (Cyrillic)) --- sr/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 sr/state_of_js_2020.yml diff --git a/sr/state_of_js_2020.yml b/sr/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/sr/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 3806c5c055943fd355016bb5f1298a9bf4fb8e55 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:51 +0900 Subject: [PATCH 0353/1932] New translations state_of_js_2020_survey.yml (Spanish) --- es/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 es/state_of_js_2020_survey.yml diff --git a/es/state_of_js_2020_survey.yml b/es/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/es/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 5756e64e2828ff97f807771cdc5afa5dda1d8d6c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:52 +0900 Subject: [PATCH 0354/1932] New translations state_of_js_2020.yml (Swedish) --- sv/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 sv/state_of_js_2020.yml diff --git a/sv/state_of_js_2020.yml b/sv/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/sv/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 98856c174098bc3452d64c09cb2c3f97c9402828 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:52 +0900 Subject: [PATCH 0355/1932] New translations state_of_js_2020.yml (Turkish) --- tr/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 tr/state_of_js_2020.yml diff --git a/tr/state_of_js_2020.yml b/tr/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/tr/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 98c47b23422538898447ba4c5a3e7ca32b62f94e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:53 +0900 Subject: [PATCH 0356/1932] New translations state_of_js_2020.yml (Ukrainian) --- uk/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 uk/state_of_js_2020.yml diff --git a/uk/state_of_js_2020.yml b/uk/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/uk/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 9a5be556a1eff49e808c5a7d0af9bd6b992e7caa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:54 +0900 Subject: [PATCH 0357/1932] New translations state_of_js_2020.yml (Chinese Simplified) --- zh/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 zh/state_of_js_2020.yml diff --git a/zh/state_of_js_2020.yml b/zh/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/zh/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 27a39cd3e523db54009e787ee9ae8c72dac3bd02 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:56 +0900 Subject: [PATCH 0358/1932] New translations state_of_js_2020.yml (English) --- en/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 en/state_of_js_2020.yml diff --git a/en/state_of_js_2020.yml b/en/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/en/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From b4b3cd9c89b7058473f700fe539677bd787b2283 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:56 +0900 Subject: [PATCH 0359/1932] New translations state_of_js_2020.yml (Vietnamese) --- vi/state_of_js_2020.yml | 303 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 303 insertions(+) create mode 100644 vi/state_of_js_2020.yml diff --git a/vi/state_of_js_2020.yml b/vi/state_of_js_2020.yml new file mode 100644 index 00000000000..b5d9d828507 --- /dev/null +++ b/vi/state_of_js_2020.yml @@ -0,0 +1,303 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The annual survey about the latest trends in the JavaScript ecosystem. + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + As crappy as 2020 was, JavaScript as a whole still managed to somehow move forward. As the language itself keeps improving + thanks to new features like Optional Chaining and Nullish Coalescing, TypeScript's widespread adoption is taking things to a whole other level by popularizing static typing. + + And on the framework side, just when we thought things were settling down, Svelte comes in and shakes everything up with a fresh take on the front-end. And even build tools are showing signs of new activity after years of webpack dominance. + + But the difference this time is that the “old” guard –relatively speaking– is not going anywhere. Svelte and Snowpack are great, but so are React and webpack. And sure, they too will eventually fall prey to the Great JavaScript Churn, but not for many, many years. + + So let's enjoy what we have here: a great ecosystem that just keeps getting even better! + + ### Join Our Launch Livestream! + + We'll be doing a [special launch livestream](https://stateofjs.com/2020stream/) in collaboration with the folks at the CodeItLive Twitch channel. Join us along with guests such as Sarah Drasner, Josh W. Comeau, and Kent C. Dodds to discuss this past year's JavaScript trends! + + ### Download Our Data + + You can [download the raw JSON data for this survey](https://www.kaggle.com/sachag/state-of-js). Let us know if you end up making your own data visualizations! + + ### State of CSS + + If you haven't seen it already, we strongly recommend checking out the [State of CSS 2020 Trend Report](https://2020.stateofcss.com/en-US/report/) to get up to date on the past year's three main CSS trends. + + ### Thanks + + Many thanks to [Alexey Pyltsyn](https://github.com/lex111) for his help with translations. + + Thanks as well to [Amelia Wattenberger](https://wattenberger.com/) for helping us update her original “Changes Over Time” chart from last year. If you want to learn how to build your own amazing data visualizations there's no better way than her [D3 video course](https://www.newline.co/fullstack-d3). + + ### Credits & Stuff + + The State of JavaScript Survey is created and maintained by [Sacha Greif](https://twitter.com/sachagreif) and [Raphaël Benitte](https://twitter.com/benitteraphael). + + Watch [this video overview](https://www.youtube.com/watch?v=o4w1qEnZxbM) to learn more about the technical aspects of the project, from data collection to data visualizations. Questions? Feedback? [Get in touch](mailto:hello@stateofjs.com) or [join our Discord](https://discord.gg/zRDb35jfrt). + + And now, let's see what JavaScript has been up to this year! + + – Sacha and Raphaël + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the survey and look good in the process! + + We've updated last year's very popular 👕 State of JavaScript T-shirt 👕 for + the 2020 JavaScript landscape! + + The shirt features a ”periodic table of JavaScript” that lists the most popular + libraries grouped by category, along with their GitHub stars counts (in thousands). + + This shirt is a great way to familiarize yourself with the JavaScript ecosystem, + and maybe even strike up a conversation with other like-minded + JavaScript developers! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + Printing and shipping is handled by [Cotton Bureau](https://cottonbureau.com/people/state-of-js). The design is printed on a premium Next Level black super-soft, tri-blend shirt. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD ${price} + shipping + - + ########################################################################### + #Sections Introductions + ########################################################################### + key: sections.user_info.description + t: | + This year's survey reached **23,765** people in **137** countries. For the first time this year, + we were able to translate the survey questions in multiple languages thanks to an awesome team of volunteers. + - + key: sections.features.description + t: | + While most respondents were aware of the majority of JavaScript features + mentioned in the survey, many still have yet to actually use most of them. + - + key: sections.technologies.description + t: | + The typical new JavaScript library shows high satisfaction but low usage, which can sometimes make + selecting the right technology for your needs a bit tricky. This is where looking at + the data can really help point you in the right direction. + - + key: sections.javascript_flavors.description + t: | + The trend of “flavors” of JavaScript that compile down to standard code started all these + years ago with CoffeeScript, but it's now clear that TypeScript is the uncontested leader in + that category. + - + key: sections.front_end_frameworks.description + t: | + As usual React and Vue lead the pack, but Svelte is quickly establishing itself as a very + serious contender for the front-end crown. + - + key: sections.datalayer.description + t: | + While the datalayer space is still in constant movement, one thing seems clear: GraphQL and + its related technologies are here to stay. + - + key: sections.back_end_frameworks.description + t: | + The back-end space is still very fragmented, but Express stands out as the one dominant + tool, while Next.js maintains its high satisfaction ratio. + - + key: sections.testing.description + t: | + The testing ecosystem keeps getting richer, with new entrants Testing Library and Playwright both + scoring high marks on the satisfaction index. + - + key: sections.build_tools.description + t: | + Just when it seemed like webpack's dominance had settled the debate, the build tools scene + has again exploded with new entrants like Snowpack and esbuild, leading us to give it a full + section for the first time since 2017. + - + key: sections.mobile_desktop.description + t: | + JavaScript is not just for the browser, and while Electron and React Native are the two + best-known names in this category, other solutions like Expo and Capacitor are also starting + to make waves. + - + key: sections.other_tools.description + t: | + The diversity and quantity of libraries, utilities, and other tools highlights how vast the JavaScript + ecosystem has become, and for the first time this year we're also tracking JavaScript runtimes + such as Deno and Hermes. + - + key: sections.resources.description + t: | + Many great resources are listed here, and we're sure that you'll find at least a few new + blogs or podcasts to follow! + - + key: sections.opinions.description + t: | + While things are generally looking good in JavaScript land, there does seem to be a bit of a + come-down from the positivity high-point of 2018. Will the trend persist? Tune in next year to find out! + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list; also matches `email`, `by email`, etc. + - State of CSS: the [State of CSS](https://stateofcss.com/) mailing list + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + #- key: award.feature_adoption_delta_award.comment + #t: With a **{value}** progression in 2020, this was the year CSS Grid crossed over from new technology to established tool. + key: award.tool_usage_delta_award.comment + t: TypeScript was already popular, and with a **{value}** growth in usage it looks like it's only going to get more ubiquitous going forward. + - + key: award.tool_satisfaction_award.comment + t: With a sky-high satisfaction rating of **{value}**, Testing Library is 2020's overall most beloved tool. + - + key: award.tool_interest_award.comment + t: GraphQL continues to be the one thing developers want to learn more about with an interest ratio of **{value}**, as soon as they can finally find the time. + - + key: award.most_write_ins_award.comment + t: People are always passionate about text editors, and with **{value}** mentions IntelliJ IDEA wins the award for the most write-in answers. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + Since ancient times, philosophers have pondered the Paradox of JavaScript: on one hand, you can't wait for exciting new language features and libraries that promise to make your developer experience so much better. + + But at the same time, you crave stability and simplicity so you can finally get things done without having to spend half your time browsing through convoluted GitHub issues threads and outdated Stack Overflow questions. + + So which is it? Do we want the new shiny, or the old reliable? More than ever, 2020 shows that we won't settle for anything less than *both*. The good news is that the JavaScript community has risen up to the challenge, which promises an exciting 2021! + + P.S. if you're still hungry for more JavaScript stats we recommend checking out the yearly [Rising Stars](https://risingstars.js.org/2020/en/) rankings from [Best Of JS](https://bestofjs.org/). + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_2020_pick + t: 'My 2020 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.joshwcomeau.bio + t: Software-engineer-turned-educator + - + key: picks.joshwcomeau.description + t: | + This is a fantastic intro resource for learning about web accessibility! + I picked it because it's our job as JS devs to make sure that the sites + we build are usable by everyone, not just sighted keyboard-and-mouse users. + - + key: picks.swyx.bio + t: Infinite Builder + - + key: picks.swyx.description + t: | + Svelte is the Space Elevator of frontend frameworks. + It helps you ship apps extremely fast. + - + key: picks.kentcdodds.bio + t: Improving the world with quality software + - + key: picks.kentcdodds.description + t: | + Remix is a different approach to React frameworks with an emphasis on progressive + enhancement. It embraces the web platform in a way that no existing frameworks do + and I'm excited by its potential. + - + key: picks.sarah_edo.bio + t: Core Team Vue.js + - + key: picks.sarah_edo.description + t: | + Insomnia is an app that allows you to design, test, and deploy API + Workflows with a clean, simplified UX- it has both REST and GraphQL support, + though clearly the puns are better if you're using REST. + - + key: picks.ladyleet.bio + t: This Dot Labs, GDE, MVP + - + key: picks.ladyleet.description + t: | + RedwoodJS and frameworks like it are starting to change how we think about development. + It’s bringing the ease of Ruby on Rails to the front-end ecosystem. + - + key: picks.midudev.bio + t: Lead Frontend @ Adevinta & Content Creator + - + key: picks.midudev.description + t: | + Working with modules on the JavaScript ecosystem has been messy. + ES2020 came with ES Modules to end that. Even it's stable on Node.js. Yei! + - + key: picks.cassidoo.bio + t: Principal Developer Experience Engineer at Netlify + - + key: picks.cassidoo.description + t: | + Ben is one of the most generous people in the JS community. + He's active in open source (on the Vue core team), + consistently makes useful content for developers to learn, and is very giving with his time. + - + key: picks.lauragift_.bio + t: Frontend Developer @ PassionatePeople + - + key: picks.lauragift_.description + t: | + Josh Comeau has been an inspiration to me, and I can say the JS community in general. + He writes very thoughtful articles on his blog, and they are some of the best I read in + 2020 because they either helped me stay on top of the latest in JavaScript + or helped me learn something new. + - + key: picks.tomdale.bio + t: JavaScript Thinkfluencer + - + key: picks.tomdale.description + t: | + Volta helps manage your entire JavaScript toolchain – think nvm, but it also helps + you and your team stay on the same versions of Node, npm, CLI tools, etc. + I love it because it's so darn nice to use, and is pioneering the use of + Rust to build speedy tools for JS. + - + key: picks.markdalgleish.bio + t: Co-creator of CSS Modules, creator of Playroom + - + key: picks.markdalgleish.description + t: | + Automates npm publishing with the ability to tie Markdown release notes to every change. Changesets has really leveled up the quality of our release notes and version management this year. + - + key: picks.sachagreif.bio + t: Creator of the State of JS survey + - + key: picks.sachagreif.description + t: | + Best Of JS tracks GitHub stats about virtually every major JavaScript project, and it has been an invaluable resource for helping us decide what to include in the survey! From 1eaaadb8b72cd21b74e185ece4aa3ceb32aa21b5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:58 +0900 Subject: [PATCH 0360/1932] New translations state_of_js_2020_survey.yml (Romanian) --- ro/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ro/state_of_js_2020_survey.yml diff --git a/ro/state_of_js_2020_survey.yml b/ro/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/ro/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 0608c6c563933ee335cae1584a423055d7a6fd2d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:06:59 +0900 Subject: [PATCH 0361/1932] New translations state_of_js_2020_survey.yml (French) --- fr/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 fr/state_of_js_2020_survey.yml diff --git a/fr/state_of_js_2020_survey.yml b/fr/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/fr/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From b4b73efe1d814651d1c7587a28d420ae760c0256 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:00 +0900 Subject: [PATCH 0362/1932] New translations state_of_js_2020_survey.yml (Afrikaans) --- af/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 af/state_of_js_2020_survey.yml diff --git a/af/state_of_js_2020_survey.yml b/af/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/af/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 8e83fbf2040daf33cb000578b9903f18866fa028 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:01 +0900 Subject: [PATCH 0363/1932] New translations state_of_js_2020_survey.yml (Japanese) --- ja/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ja/state_of_js_2020_survey.yml diff --git a/ja/state_of_js_2020_survey.yml b/ja/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/ja/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From d9f4d05627d2354756601c3e420ac120b75835ca Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:02 +0900 Subject: [PATCH 0364/1932] New translations state_of_js_2020_survey.yml (Arabic) --- ar/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ar/state_of_js_2020_survey.yml diff --git a/ar/state_of_js_2020_survey.yml b/ar/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/ar/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 8fa9d4229ee79ba09f51395713c5e0bebc08dc2d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:03 +0900 Subject: [PATCH 0365/1932] New translations state_of_js_2020_survey.yml (Catalan) --- ca/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 ca/state_of_js_2020_survey.yml diff --git a/ca/state_of_js_2020_survey.yml b/ca/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/ca/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 8469dc427a413d61373ad9fea283aab1088ad81a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:04 +0900 Subject: [PATCH 0366/1932] New translations state_of_js_2020_survey.yml (Czech) --- cs/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 cs/state_of_js_2020_survey.yml diff --git a/cs/state_of_js_2020_survey.yml b/cs/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/cs/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From d910f4394db36d0bfbe41b7cfc26df0e1d1815b1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:05 +0900 Subject: [PATCH 0367/1932] New translations state_of_js_2020_survey.yml (Danish) --- da/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 da/state_of_js_2020_survey.yml diff --git a/da/state_of_js_2020_survey.yml b/da/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/da/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 989b10781743eebc7debc0c2913d5550a01db40d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:06 +0900 Subject: [PATCH 0368/1932] New translations state_of_js_2020_survey.yml (German) --- de/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 de/state_of_js_2020_survey.yml diff --git a/de/state_of_js_2020_survey.yml b/de/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/de/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 8ea429b29eb003f9732d2f280da65d5dc8cd492e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:07 +0900 Subject: [PATCH 0369/1932] New translations state_of_js_2020_survey.yml (Greek) --- el/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 el/state_of_js_2020_survey.yml diff --git a/el/state_of_js_2020_survey.yml b/el/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/el/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From bca432a9f49ee2b1d1eb9250077753c41329b072 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:08 +0900 Subject: [PATCH 0370/1932] New translations state_of_js_2020_survey.yml (Finnish) --- fi/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 fi/state_of_js_2020_survey.yml diff --git a/fi/state_of_js_2020_survey.yml b/fi/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/fi/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From b3b6f6fce572b604c8d0fa51fedd005df2b1507b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:08 +0900 Subject: [PATCH 0371/1932] New translations state_of_js_2020_survey.yml (Hebrew) --- he/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 he/state_of_js_2020_survey.yml diff --git a/he/state_of_js_2020_survey.yml b/he/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/he/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 41d56dbe785d42c0bf74be15e25b093f44476201 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:09 +0900 Subject: [PATCH 0372/1932] New translations state_of_js_2020_survey.yml (Hungarian) --- hu/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 hu/state_of_js_2020_survey.yml diff --git a/hu/state_of_js_2020_survey.yml b/hu/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/hu/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 9980fc342c0f38360d38b0a95c72683ac8033057 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:10 +0900 Subject: [PATCH 0373/1932] New translations state_of_js_2020_survey.yml (Italian) --- it/state_of_js_2020_survey.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 it/state_of_js_2020_survey.yml diff --git a/it/state_of_js_2020_survey.yml b/it/state_of_js_2020_survey.yml new file mode 100644 index 00000000000..59966deb8b7 --- /dev/null +++ b/it/state_of_js_2020_survey.yml @@ -0,0 +1,13 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2020 + t: > + 2020 has been a tough year for everyone, one that makes worrying about the latest JavaScript frameworks seem pretty futile in comparison. + + Still, the world has to move on, and so does JavaScript. And once again, with your help we'll try to build a comprehensive picture of the ecosystem to find out a little bit more about where it's going. From 5f9585c622bd2005c18149c36cc56a353872c253 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:11 +0900 Subject: [PATCH 0374/1932] New translations state_of_js_2021_results.yml (Greek) --- el/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 el/state_of_js_2021_results.yml diff --git a/el/state_of_js_2021_results.yml b/el/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/el/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 8b32e03ff1c2e007f429438f76d7080710307618 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:12 +0900 Subject: [PATCH 0375/1932] New translations state_of_js_2021_results.yml (Finnish) --- fi/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 fi/state_of_js_2021_results.yml diff --git a/fi/state_of_js_2021_results.yml b/fi/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/fi/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 9b94d50c04f230ee69465d04aef705d85f317817 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:13 +0900 Subject: [PATCH 0376/1932] New translations state_of_js_2021_survey.yml (Norwegian) --- no/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 no/state_of_js_2021_survey.yml diff --git a/no/state_of_js_2021_survey.yml b/no/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/no/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 07a013a0449a3fd50f8d41393f8b7dc6748846b4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:14 +0900 Subject: [PATCH 0377/1932] New translations state_of_js_2021_survey.yml (German) --- de/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 de/state_of_js_2021_survey.yml diff --git a/de/state_of_js_2021_survey.yml b/de/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/de/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 0b636b98f0cddc1d3ff6b9e9cae52fd5a7170b9a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:14 +0900 Subject: [PATCH 0378/1932] New translations state_of_js_2021_survey.yml (Greek) --- el/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 el/state_of_js_2021_survey.yml diff --git a/el/state_of_js_2021_survey.yml b/el/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/el/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 630788beb6031cc04d855f55577b409853162948 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:15 +0900 Subject: [PATCH 0379/1932] New translations state_of_js_2021_survey.yml (Finnish) --- fi/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 fi/state_of_js_2021_survey.yml diff --git a/fi/state_of_js_2021_survey.yml b/fi/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/fi/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 67439a089541fe79cd6c48921ba3f6808c267cc2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:16 +0900 Subject: [PATCH 0380/1932] New translations state_of_js_2021_survey.yml (Hebrew) --- he/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 he/state_of_js_2021_survey.yml diff --git a/he/state_of_js_2021_survey.yml b/he/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/he/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 8e6ad0fed11fb4347957d9d43e451341de222615 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:17 +0900 Subject: [PATCH 0381/1932] New translations state_of_js_2021_survey.yml (Hungarian) --- hu/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 hu/state_of_js_2021_survey.yml diff --git a/hu/state_of_js_2021_survey.yml b/hu/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/hu/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 7cb4ac0f1bda9934499888f3d58550a94180d3d6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:18 +0900 Subject: [PATCH 0382/1932] New translations state_of_js_2021_survey.yml (Italian) --- it/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 it/state_of_js_2021_survey.yml diff --git a/it/state_of_js_2021_survey.yml b/it/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/it/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 73dd81830929f020834379b5accbc38ed83e409d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:19 +0900 Subject: [PATCH 0383/1932] New translations state_of_js_2021_survey.yml (Japanese) --- ja/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 ja/state_of_js_2021_survey.yml diff --git a/ja/state_of_js_2021_survey.yml b/ja/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/ja/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 9a709964951ec5410aa15592fff59efb524454f7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:19 +0900 Subject: [PATCH 0384/1932] New translations state_of_js_2021_survey.yml (Korean) --- ko/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 ko/state_of_js_2021_survey.yml diff --git a/ko/state_of_js_2021_survey.yml b/ko/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/ko/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 85789d84d1e8c6c5a3f666b98384ef2da4283312 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:20 +0900 Subject: [PATCH 0385/1932] New translations state_of_js_2021_survey.yml (Dutch) --- nl/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 nl/state_of_js_2021_survey.yml diff --git a/nl/state_of_js_2021_survey.yml b/nl/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/nl/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 266c9891ec1794966204804c36f4459c9a91c00b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:21 +0900 Subject: [PATCH 0386/1932] New translations state_of_js_2021_survey.yml (Polish) --- pl/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 pl/state_of_js_2021_survey.yml diff --git a/pl/state_of_js_2021_survey.yml b/pl/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/pl/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From ac4d0b2764daa31fbb12f29001f678683f291871 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:22 +0900 Subject: [PATCH 0387/1932] New translations state_of_js_2021_survey.yml (Czech) --- cs/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 cs/state_of_js_2021_survey.yml diff --git a/cs/state_of_js_2021_survey.yml b/cs/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/cs/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From beea0932e8bae004c11d42260e5d93b437e254d9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:23 +0900 Subject: [PATCH 0388/1932] New translations state_of_js_2021_survey.yml (Portuguese) --- pt/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 pt/state_of_js_2021_survey.yml diff --git a/pt/state_of_js_2021_survey.yml b/pt/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/pt/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 373d202dd5dadc05fe335affc518a5dcb6aebac3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:23 +0900 Subject: [PATCH 0389/1932] New translations state_of_js_2021_survey.yml (Russian) --- ru/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 ru/state_of_js_2021_survey.yml diff --git a/ru/state_of_js_2021_survey.yml b/ru/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/ru/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 81cf80bac9e96c7e5814abece4bba4777b30ed2d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:24 +0900 Subject: [PATCH 0390/1932] New translations state_of_js_2021_survey.yml (Serbian (Cyrillic)) --- sr/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 sr/state_of_js_2021_survey.yml diff --git a/sr/state_of_js_2021_survey.yml b/sr/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/sr/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From e68a3751f1ff1002a51baeb9a2f6ddfb83cccbf0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:25 +0900 Subject: [PATCH 0391/1932] New translations state_of_js_2021_survey.yml (Swedish) --- sv/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 sv/state_of_js_2021_survey.yml diff --git a/sv/state_of_js_2021_survey.yml b/sv/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/sv/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 9056ec342514097cfdb6866e76d78f60ff168082 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:26 +0900 Subject: [PATCH 0392/1932] New translations state_of_js_2021_survey.yml (Turkish) --- tr/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 tr/state_of_js_2021_survey.yml diff --git a/tr/state_of_js_2021_survey.yml b/tr/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/tr/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 2e54bf01ec3f33ebede85fa561be068e4082d6f0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:27 +0900 Subject: [PATCH 0393/1932] New translations state_of_js_2021_survey.yml (Ukrainian) --- uk/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 uk/state_of_js_2021_survey.yml diff --git a/uk/state_of_js_2021_survey.yml b/uk/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/uk/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From a33e74d9d15d6c7d3fa2790d9a17e7cbd6d58e81 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:28 +0900 Subject: [PATCH 0394/1932] New translations state_of_js_2021_survey.yml (Chinese Simplified) --- zh/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 zh/state_of_js_2021_survey.yml diff --git a/zh/state_of_js_2021_survey.yml b/zh/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/zh/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 2bbfdddb81ccb34c8ca03c405632b40ab9ab8474 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:29 +0900 Subject: [PATCH 0395/1932] New translations state_of_js_2021_survey.yml (English) --- en/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 en/state_of_js_2021_survey.yml diff --git a/en/state_of_js_2021_survey.yml b/en/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/en/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From d19ac852a9d33bc025ca508afdc5bab75a2a647d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:30 +0900 Subject: [PATCH 0396/1932] New translations state_of_js_2021_survey.yml (Vietnamese) --- vi/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 vi/state_of_js_2021_survey.yml diff --git a/vi/state_of_js_2021_survey.yml b/vi/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/vi/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 02bff3e874a569eedce42ad9bd656e29bc8f4476 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:31 +0900 Subject: [PATCH 0397/1932] New translations state_of_js_2021_survey.yml (Danish) --- da/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 da/state_of_js_2021_survey.yml diff --git a/da/state_of_js_2021_survey.yml b/da/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/da/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 57298ca2585fa43ef6b51a9e09ba5066eeeabd8d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:32 +0900 Subject: [PATCH 0398/1932] New translations state_of_js_2021_survey.yml (Catalan) --- ca/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 ca/state_of_js_2021_survey.yml diff --git a/ca/state_of_js_2021_survey.yml b/ca/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/ca/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 7dd97a28a35a2411605d850e5d5613c2cd5cb0cc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:33 +0900 Subject: [PATCH 0399/1932] New translations state_of_js_2021_results.yml (Hebrew) --- he/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 he/state_of_js_2021_results.yml diff --git a/he/state_of_js_2021_results.yml b/he/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/he/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 0abc5ac60985dd6e26158f421e7179bc2a0fa35c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:34 +0900 Subject: [PATCH 0400/1932] New translations state_of_js_2021_results.yml (Swedish) --- sv/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 sv/state_of_js_2021_results.yml diff --git a/sv/state_of_js_2021_results.yml b/sv/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/sv/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 16241ff5ba2b80672c64f9bc8ce817748d3f1b60 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:34 +0900 Subject: [PATCH 0401/1932] New translations state_of_js_2021_results.yml (Hungarian) --- hu/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 hu/state_of_js_2021_results.yml diff --git a/hu/state_of_js_2021_results.yml b/hu/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/hu/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 4cbdbef9538fc563f5b847521ed7d3610136375b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:35 +0900 Subject: [PATCH 0402/1932] New translations state_of_js_2021_results.yml (Italian) --- it/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 it/state_of_js_2021_results.yml diff --git a/it/state_of_js_2021_results.yml b/it/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/it/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From d4a19f5b35d9651ebfe48f3a04b417803be1f184 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:36 +0900 Subject: [PATCH 0403/1932] New translations state_of_js_2021_results.yml (Japanese) --- ja/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 ja/state_of_js_2021_results.yml diff --git a/ja/state_of_js_2021_results.yml b/ja/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/ja/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From b481adfa61a298e4307bdfb85553219b82987aaf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:37 +0900 Subject: [PATCH 0404/1932] New translations state_of_js_2021_results.yml (Korean) --- ko/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 ko/state_of_js_2021_results.yml diff --git a/ko/state_of_js_2021_results.yml b/ko/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/ko/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From aec525a57ed2d009c1f346101939727cabb722f1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:38 +0900 Subject: [PATCH 0405/1932] New translations state_of_js_2021_results.yml (Dutch) --- nl/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 nl/state_of_js_2021_results.yml diff --git a/nl/state_of_js_2021_results.yml b/nl/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/nl/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 7db1da8f355dc69cd63c5e66cc2c924e5f0f52c2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:39 +0900 Subject: [PATCH 0406/1932] New translations state_of_js_2021_results.yml (Norwegian) --- no/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 no/state_of_js_2021_results.yml diff --git a/no/state_of_js_2021_results.yml b/no/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/no/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 074f7908f66bed0d54ac6709c6ac3e941b057eeb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:40 +0900 Subject: [PATCH 0407/1932] New translations state_of_js_2021_results.yml (Polish) --- pl/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 pl/state_of_js_2021_results.yml diff --git a/pl/state_of_js_2021_results.yml b/pl/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/pl/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 5be11092f6743dfff82093e075d1220b51e867c6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:41 +0900 Subject: [PATCH 0408/1932] New translations state_of_js_2021_results.yml (Portuguese) --- pt/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 pt/state_of_js_2021_results.yml diff --git a/pt/state_of_js_2021_results.yml b/pt/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/pt/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 2b29922e2618b204c9a8404416d4cae9fafb34ff Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:42 +0900 Subject: [PATCH 0409/1932] New translations state_of_js_2021_results.yml (Russian) --- ru/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 ru/state_of_js_2021_results.yml diff --git a/ru/state_of_js_2021_results.yml b/ru/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/ru/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 518681a95c9a673f828eb4b37b0190b485d74b5a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:43 +0900 Subject: [PATCH 0410/1932] New translations state_of_js_2021_results.yml (Serbian (Cyrillic)) --- sr/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 sr/state_of_js_2021_results.yml diff --git a/sr/state_of_js_2021_results.yml b/sr/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/sr/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 47dd8f998d51eff0608caba7d46c61c8ac0ae1de Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:44 +0900 Subject: [PATCH 0411/1932] New translations state_of_js_2021_results.yml (Turkish) --- tr/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 tr/state_of_js_2021_results.yml diff --git a/tr/state_of_js_2021_results.yml b/tr/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/tr/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 524aabb1a0d44b235c1527993f10aad34c74f217 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:44 +0900 Subject: [PATCH 0412/1932] New translations state_of_js_2021_survey.yml (Arabic) --- ar/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 ar/state_of_js_2021_survey.yml diff --git a/ar/state_of_js_2021_survey.yml b/ar/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/ar/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 0c22f3c91aeab8161595df8be0d659d55c327adb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:46 +0900 Subject: [PATCH 0413/1932] New translations state_of_js_2021_results.yml (Ukrainian) --- uk/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 uk/state_of_js_2021_results.yml diff --git a/uk/state_of_js_2021_results.yml b/uk/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/uk/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 8a01a365d9e94f5eab108a10deeffaf7c3e585a2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:47 +0900 Subject: [PATCH 0414/1932] New translations state_of_js_2021_results.yml (Chinese Simplified) --- zh/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 zh/state_of_js_2021_results.yml diff --git a/zh/state_of_js_2021_results.yml b/zh/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/zh/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 56e9ba7a6b96234e2be71ceecfc14aaff8babdea Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:48 +0900 Subject: [PATCH 0415/1932] New translations state_of_js_2021_results.yml (English) --- en/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 en/state_of_js_2021_results.yml diff --git a/en/state_of_js_2021_results.yml b/en/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/en/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From c190b11e810cedebed7c90756306eb702f198dff Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:49 +0900 Subject: [PATCH 0416/1932] New translations state_of_js_2021_results.yml (Vietnamese) --- vi/state_of_js_2021_results.yml | 429 ++++++++++++++++++++++++++++++++ 1 file changed, 429 insertions(+) create mode 100644 vi/state_of_js_2021_results.yml diff --git a/vi/state_of_js_2021_results.yml b/vi/state_of_js_2021_results.yml new file mode 100644 index 00000000000..5bcff86c7d0 --- /dev/null +++ b/vi/state_of_js_2021_results.yml @@ -0,0 +1,429 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2021 edition of the annual survey about the latest trends in the JavaScript ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: | + + A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + This year, **16,085** respondents took part in the survey. And in order + to help highlight different voices and surface deeper insights, we made a special + effort to provide new ways to break our data down. + - + key: sections.features.description + t: | + JavaScript may move fast, but it seems like JavaScript developers move even faster, as many relatively new features already show high adoption levels. + - + key: sections.technologies.description + t: | + This year's results point to a high degree of fragmentation in the JavaScript world. But while this can sometimes cause headaches, all that competition does make for a very dynamic ecosystem. + - + key: sections.tools_others.description + t: | + Picking a technology can often come down to a series of tough choices between + competing priorities, and this year we tried to capture this process using a new bracket-style question format. + - + key: sections.environments.description + t: | + Accessibility has long been an after-thought when it comes to web development, but many developers + are now realizing that it should in fact be the foundation on which everything else rests. + - + key: sections.resources.description + t: | + Highlighting blogs, podcasts, and sites was a good start, but this year we decided to go one step further + and actually feature the people who make up the JavaScript community! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.language + aliasFor: sections.language.title + - + key: options.features_categories.browser_apis + aliasFor: sections.browser_apis.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2021 Pick: ' + - + key: picks.intro + t: We asked members of the JavaScript community to share their “pick of the year” + - + key: picks.lee_robinson.name + t: SvelteKit + - + key: picks.lee_robinson.bio + t: Director of Developer Relations at Vercel + - + key: picks.lee_robinson.description + t: | + SvelteKit is a fresh take on building for the web and has an + incredibly passionate, growing community of supporters. + - + key: picks.vadim_makeev.name + t: Server-Side Rendering + - + key: picks.vadim_makeev.bio + t: DevRel, Podcaster & Web Standards Advocate + - + key: picks.vadim_makeev.description + t: | + The time has come to get our priorities straight. + UX > DX, and it has always been like that. Performance FTW! + - + key: picks.ben_ilegbodu.name + t: Lee Robinson + - + key: picks.ben_ilegbodu.bio + t: Ben Ilegbodu, Principal Frontend Engineer @ Stitch Fix + - + key: picks.ben_ilegbodu.description + t: | + Lee has been great at shepherding and advocating for Next.js. + He's helped me a ton with Next and continues to build excitement + for where it's going + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 93bdf7a0f1513e8e5b2cb61fb5edfa6471e09d7d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:51 +0900 Subject: [PATCH 0417/1932] New translations state_of_js_2021_survey.yml (Romanian) --- ro/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 ro/state_of_js_2021_survey.yml diff --git a/ro/state_of_js_2021_survey.yml b/ro/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/ro/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 1eb21b08fe0d0ed3fe4f06c998ecbcf35ec056b4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:52 +0900 Subject: [PATCH 0418/1932] New translations state_of_js_2021_survey.yml (French) --- fr/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 fr/state_of_js_2021_survey.yml diff --git a/fr/state_of_js_2021_survey.yml b/fr/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/fr/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 15ddf074578446f8b005abd635d02b73fd7d8321 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:52 +0900 Subject: [PATCH 0419/1932] New translations state_of_js_2021_survey.yml (Spanish) --- es/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 es/state_of_js_2021_survey.yml diff --git a/es/state_of_js_2021_survey.yml b/es/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/es/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 50b60f3b09021f162aa2ea7c581c3ab06dfc4091 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:53 +0900 Subject: [PATCH 0420/1932] New translations state_of_js_2021_survey.yml (Afrikaans) --- af/state_of_js_2021_survey.yml | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 af/state_of_js_2021_survey.yml diff --git a/af/state_of_js_2021_survey.yml b/af/state_of_js_2021_survey.yml new file mode 100644 index 00000000000..74450897fe7 --- /dev/null +++ b/af/state_of_js_2021_survey.yml @@ -0,0 +1,26 @@ +--- +locale: en-US +namespace: js +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.survey_intro_js2021 + t: > + First the 2020 Olympics got pushed back to 2021, and now the 2021 State of JavaScript survey is happening now, in 2022! + + It's true: between work, family, and and all the turmoil in the world, some things got disrupted a little. + + But while the year may be off-by-one, we hope the data provided by the survey itself will be just as informative and insightful as ever. And don't worry, there will be another survey towards the end of this year to set things straight again! + - + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of the JavaScript language you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **frameworks** that make up the JavaScript ecosystem. Let us know what you're excited about! From 8f865380e6255babc4f43c159051714dd6d03aa1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:55 +0900 Subject: [PATCH 0421/1932] New translations surveys.yml (Romanian) --- ro/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 ro/surveys.yml diff --git a/ro/surveys.yml b/ro/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/ro/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From b112b69cd5485fb860270bd6c46e7e58768a77e0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:55 +0900 Subject: [PATCH 0422/1932] New translations surveys.yml (Dutch) --- nl/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 nl/surveys.yml diff --git a/nl/surveys.yml b/nl/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/nl/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From bf8212023b6fe86e8f3a55db4ffd6cf6a142ff88 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:57 +0900 Subject: [PATCH 0423/1932] New translations surveys.yml (Vietnamese) --- vi/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 vi/surveys.yml diff --git a/vi/surveys.yml b/vi/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/vi/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From b3943242417c9600a6788e71dbf1bb51203c3a12 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:57 +0900 Subject: [PATCH 0424/1932] New translations surveys.yml (English) --- en/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 en/surveys.yml diff --git a/en/surveys.yml b/en/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/en/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 00029fcee67c7b6bba0cf29667398b4381b90a60 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:07:58 +0900 Subject: [PATCH 0425/1932] New translations surveys.yml (Chinese Traditional) --- zh/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 zh/surveys.yml diff --git a/zh/surveys.yml b/zh/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/zh/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 9d5c2cfcf66bb18e5217987f897e22ee865f361c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:00 +0900 Subject: [PATCH 0426/1932] New translations surveys.yml (Ukrainian) --- uk/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 uk/surveys.yml diff --git a/uk/surveys.yml b/uk/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/uk/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 508b963a93a5c2212552b47c3556c0d75a0e8edc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:01 +0900 Subject: [PATCH 0427/1932] New translations surveys.yml (Turkish) --- tr/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 tr/surveys.yml diff --git a/tr/surveys.yml b/tr/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/tr/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 0627f445c0f7de6388e7fbcaddd68f46276d8f22 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:02 +0900 Subject: [PATCH 0428/1932] New translations surveys.yml (Swedish) --- sv/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 sv/surveys.yml diff --git a/sv/surveys.yml b/sv/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/sv/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 8435b7c02e7770d0c46fca0a953c23a758c49d8f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:02 +0900 Subject: [PATCH 0429/1932] New translations surveys.yml (Serbian (Cyrillic)) --- sr/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 sr/surveys.yml diff --git a/sr/surveys.yml b/sr/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/sr/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From c1f4ef60a1bf30ce4d2923270758d0d66d53a1e0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:03 +0900 Subject: [PATCH 0430/1932] New translations surveys.yml (Russian) --- ru/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 ru/surveys.yml diff --git a/ru/surveys.yml b/ru/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/ru/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 38f37044bf670b3a78313eb2a113bc2852e6ab6b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:04 +0900 Subject: [PATCH 0431/1932] New translations surveys.yml (Portuguese) --- pt/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 pt/surveys.yml diff --git a/pt/surveys.yml b/pt/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/pt/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 1689a317fc8a1acdd8b4337735a1ab7704acfbf7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:05 +0900 Subject: [PATCH 0432/1932] New translations surveys.yml (Polish) --- pl/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 pl/surveys.yml diff --git a/pl/surveys.yml b/pl/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/pl/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 964620f14e6725fd3775e79b7578dbb4ab8949fd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:06 +0900 Subject: [PATCH 0433/1932] New translations surveys.yml (Norwegian) --- no/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 no/surveys.yml diff --git a/no/surveys.yml b/no/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/no/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 5375482afdbabcd56bd079a9e9b5d09afbe20ae0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:07 +0900 Subject: [PATCH 0434/1932] New translations surveys.yml (Korean) --- ko/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 ko/surveys.yml diff --git a/ko/surveys.yml b/ko/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/ko/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 97424f7390569db20c86b4413138af660c6e2870 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:08 +0900 Subject: [PATCH 0435/1932] New translations surveys.yml (French) --- fr/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 fr/surveys.yml diff --git a/fr/surveys.yml b/fr/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/fr/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From b0e60bfe911e76ef1d873cf3915d0d62fd4f81d2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:09 +0900 Subject: [PATCH 0436/1932] New translations surveys.yml (Japanese) --- ja/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 ja/surveys.yml diff --git a/ja/surveys.yml b/ja/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/ja/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 88c117b7800bd29341028a70b010f9e5dc1c981c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:09 +0900 Subject: [PATCH 0437/1932] New translations surveys.yml (Italian) --- it/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 it/surveys.yml diff --git a/it/surveys.yml b/it/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/it/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 222f1bd0eafb2bfbf23abe9ce110b1f16d5ff2e9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:10 +0900 Subject: [PATCH 0438/1932] New translations surveys.yml (Hungarian) --- hu/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 hu/surveys.yml diff --git a/hu/surveys.yml b/hu/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/hu/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 27197ff774d824cef6ba46d0353f783373d7cdd3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:11 +0900 Subject: [PATCH 0439/1932] New translations surveys.yml (Hebrew) --- he/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 he/surveys.yml diff --git a/he/surveys.yml b/he/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/he/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 81a60c082a1a0139bf886d8c4d953b68f2492854 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:12 +0900 Subject: [PATCH 0440/1932] New translations surveys.yml (Finnish) --- fi/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 fi/surveys.yml diff --git a/fi/surveys.yml b/fi/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/fi/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From c021bbe7caedbd339fa470ce3face44c95c3f905 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:13 +0900 Subject: [PATCH 0441/1932] New translations surveys.yml (Greek) --- el/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 el/surveys.yml diff --git a/el/surveys.yml b/el/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/el/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From dbe3532b909b7f9a0b83fb4b5ffe7670fc831b90 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:14 +0900 Subject: [PATCH 0442/1932] New translations surveys.yml (German) --- de/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 de/surveys.yml diff --git a/de/surveys.yml b/de/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/de/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 76064ef2b48fbd4d8680310065dae0df60617189 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:15 +0900 Subject: [PATCH 0443/1932] New translations surveys.yml (Danish) --- da/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 da/surveys.yml diff --git a/da/surveys.yml b/da/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/da/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 8596a3d47937448bd9a3819ba5f89ee424b629d4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:16 +0900 Subject: [PATCH 0444/1932] New translations surveys.yml (Czech) --- cs/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 cs/surveys.yml diff --git a/cs/surveys.yml b/cs/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/cs/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 33e06d290db64e9c1ecc6036b74878fdde799b64 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:16 +0900 Subject: [PATCH 0445/1932] New translations surveys.yml (Catalan) --- ca/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 ca/surveys.yml diff --git a/ca/surveys.yml b/ca/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/ca/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From 441a3435f4f906230a5c6de4009b96bed8560c0d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:17 +0900 Subject: [PATCH 0446/1932] New translations surveys.yml (Arabic) --- ar/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 ar/surveys.yml diff --git a/ar/surveys.yml b/ar/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/ar/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From eaf7517f2c5dbc9bd183524e6d95fdc23253106d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:18 +0900 Subject: [PATCH 0447/1932] New translations surveys.yml (Afrikaans) --- af/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 af/surveys.yml diff --git a/af/surveys.yml b/af/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/af/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From a96fe8ccffeedaedd83aa48d8d4cb447b5c864b5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 24 Feb 2022 13:08:19 +0900 Subject: [PATCH 0448/1932] New translations surveys.yml (Spanish) --- es/surveys.yml | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) create mode 100644 es/surveys.yml diff --git a/es/surveys.yml b/es/surveys.yml new file mode 100644 index 00000000000..99cb51b8c6f --- /dev/null +++ b/es/surveys.yml @@ -0,0 +1,92 @@ +--- +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.no_preview_surveys + t: No surveys to preview + - + key: general.global_nav + t: Global + - + ########################################################################### + #FAQ + ########################################################################### + key: general.faq + t: FAQ + - + key: faq.create_account + t: Why do I need to create an account? + - + key: faq.create_account.description + t: We ask you to create an account in order to avoid duplicate responses, save your data, and notify you when results are published. + - + key: faq.anonymous_survey + t: Can I take the survey anonymously? + - + key: faq.anonymous_survey.description + t: Yes, you can use a fake (something@example.com) or non-identifying email to take the survey as long as you save it for future access. + - + key: faq.questions_required + t: Is answering every question required? + - + key: faq.questions_required.description + t: No, every question of the survey is optional and can freely be skipped. + - + key: faq.data_published + t: Will my data be made public? + - + key: faq.data_published.description + t: Yes, all data will be released publicly, but only after being purged of any identifying information (emails, usernames, IDs, etc.). + - + key: faq.survey_design + t: How are the surveys designed? + - + key: faq.survey_design.description + t: Surveys are designed based on community feedback, as well as reviewed by experts. You can [learn more here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - + key: faq.results_released + t: When will the results be released? + - + key: faq.results_released.description + t: Results are generally released a few weeks after the survey closes. + - + key: faq.survey_deadline + t: When will the survey close? + - + key: faq.survey_deadline.description + t: This survey is scheduled to run until {date} + - + key: faq.team + t: Who runs these surveys? + - + key: faq.team.description + t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + - + ########################################################################### + #Form Controls + ########################################################################### + key: bracket.vs + t: VS + - + key: bracket.start_over + t: Start Over + - + key: bracket.winner + t: > + + Winner: + - + key: bracket.round + t: Round + - + key: bracket.empty_bracket + t: Pending result (complete the previous round first) + - + key: bracket.result + t: Result + - + key: bracket.cancel + t: Cancel From bb3db59b9dbfc64969c3657d8f58eeaa657e9935 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:19:27 +0900 Subject: [PATCH 0449/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 fr/state_of_graphql.yml diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/fr/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 78915355b0081ad59d75a2beea3cf7234d665876 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:19:29 +0900 Subject: [PATCH 0450/1932] New translations common.yml (Spanish) --- es/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/es/common.yml b/es/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/es/common.yml +++ b/es/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 9f48323bb472266b2261b2e2d8b525482f3420e4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:19:42 +0900 Subject: [PATCH 0451/1932] New translations common.yml (Romanian) --- ro/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/ro/common.yml b/ro/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 4531112d1b962bba04e66ede103c59810c317fea Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:19:52 +0900 Subject: [PATCH 0452/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 ro/state_of_graphql.yml diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/ro/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 4d10c42a01481245ddabb75b477442ddb5a66351 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:19:54 +0900 Subject: [PATCH 0453/1932] New translations common.yml (French) --- fr/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/fr/common.yml b/fr/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 5d991a1538d2ec8659375fb98b906fe3a91cf05f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:19:59 +0900 Subject: [PATCH 0454/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 es/state_of_graphql.yml diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/es/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 12838f956088cf831689c5485db59ede731928d3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:20:01 +0900 Subject: [PATCH 0455/1932] New translations common.yml (Catalan) --- ca/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/ca/common.yml b/ca/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From a57dd629f9ea5f842035871ed8b1551a31e2a0d5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:20:07 +0900 Subject: [PATCH 0456/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 ar/state_of_graphql.yml diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/ar/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 669ebcbf54a34eb8f05797528237719840d68865 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:20:22 +0900 Subject: [PATCH 0457/1932] New translations common.yml (Afrikaans) --- af/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/af/common.yml b/af/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/af/common.yml +++ b/af/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From cec6c39c50d31cc3f5c3586ad7bd95e0feed4a4c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:20:32 +0900 Subject: [PATCH 0458/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 af/state_of_graphql.yml diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/af/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From a149723da212aa0131ef688921823210a30b8cb1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:20:35 +0900 Subject: [PATCH 0459/1932] New translations common.yml (Arabic) --- ar/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/ar/common.yml b/ar/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From fbcd1eeec1fef5d3f00503047d93b59213e9ba43 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:20:45 +0900 Subject: [PATCH 0460/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 da/state_of_graphql.yml diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/da/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 9e01cc58385dd6c2ca21f921598843dbefa9088a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:20:47 +0900 Subject: [PATCH 0461/1932] New translations common.yml (German) --- de/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/de/common.yml b/de/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/de/common.yml +++ b/de/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 80c96b7c199b1f5429567c65b45b8af0920fe965 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:20:57 +0900 Subject: [PATCH 0462/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 ca/state_of_graphql.yml diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/ca/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 0c2a1e7ccddd24c046969cc8a9076e3b02fb1b51 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:21:01 +0900 Subject: [PATCH 0463/1932] New translations common.yml (Czech) --- cs/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/cs/common.yml b/cs/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 000fb1f35b897bcd1f84ab6f683740f3dbdb0b0d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:21:14 +0900 Subject: [PATCH 0464/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 cs/state_of_graphql.yml diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/cs/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From ed9656b1387eb1806c2a8701898a1974026b51aa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:21:17 +0900 Subject: [PATCH 0465/1932] New translations common.yml (Danish) --- da/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/da/common.yml b/da/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/da/common.yml +++ b/da/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 197814de9f21980d89315622c9c2b475809151c6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:21:30 +0900 Subject: [PATCH 0466/1932] New translations common.yml (Finnish) --- fi/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/fi/common.yml b/fi/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 41a39123b43c248bbbbbeedc5b9861679daec413 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:21:32 +0900 Subject: [PATCH 0467/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 el/state_of_graphql.yml diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/el/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 585c01fd76b9e12755941ce9e5001de423c6c6a3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:21:36 +0900 Subject: [PATCH 0468/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 de/state_of_graphql.yml diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/de/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 959ba3937fc9f885389c76f2c894242596e45f7e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:21:39 +0900 Subject: [PATCH 0469/1932] New translations common.yml (Greek) --- el/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/el/common.yml b/el/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/el/common.yml +++ b/el/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 7571caec0d8f3aa5d274b4d7c88f31159d2bf002 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:21:54 +0900 Subject: [PATCH 0470/1932] New translations common.yml (Hebrew) --- he/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/he/common.yml b/he/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/he/common.yml +++ b/he/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From ae467583ac6fa155f91c4f76ddeb74236341e46d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:21:56 +0900 Subject: [PATCH 0471/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 fi/state_of_graphql.yml diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/fi/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 7a36429ca9a8e5e634933d4928b20b821cd4e82b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:21:59 +0900 Subject: [PATCH 0472/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 it/state_of_graphql.yml diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/it/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 57f5b23ca41e1ea49e8353b510c936f136dc2a64 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:22:10 +0900 Subject: [PATCH 0473/1932] New translations common.yml (Japanese) --- ja/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/ja/common.yml b/ja/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 56c60a3f572d2d17dc0273725cd2fa32263cedcd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:22:21 +0900 Subject: [PATCH 0474/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 he/state_of_graphql.yml diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/he/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From d021265924fc13f55b9361658a64e79165a7ef3c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:22:23 +0900 Subject: [PATCH 0475/1932] New translations common.yml (Hungarian) --- hu/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/hu/common.yml b/hu/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From f722ddbc3cf9e080d94c090e6a3b8987ce01ea70 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:22:33 +0900 Subject: [PATCH 0476/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 hu/state_of_graphql.yml diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/hu/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From d12c319d1ddc5d9c91e445c1bdd9ee8042423069 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:22:36 +0900 Subject: [PATCH 0477/1932] New translations common.yml (Italian) --- it/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/it/common.yml b/it/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/it/common.yml +++ b/it/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 523c7ebd438e00766417602b5d659ad18f3f7d67 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:22:45 +0900 Subject: [PATCH 0478/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 nl/state_of_graphql.yml diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/nl/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 559632c7772daa67b1badd945731fd116ab16e61 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:22:48 +0900 Subject: [PATCH 0479/1932] New translations common.yml (Norwegian) --- no/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/no/common.yml b/no/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/no/common.yml +++ b/no/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From d9b99abad20400039c58d12dd67c194385d6a305 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:22:58 +0900 Subject: [PATCH 0480/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 ja/state_of_graphql.yml diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/ja/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 10c0a880b1f0d51b99dd8f7ce56aa6b94515cf64 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:23:01 +0900 Subject: [PATCH 0481/1932] New translations common.yml (Korean) --- ko/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/ko/common.yml b/ko/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 2d6f8e60378f1a99c495a90f912961b39160c63e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:23:06 +0900 Subject: [PATCH 0482/1932] New translations common.yml (Dutch) --- nl/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/nl/common.yml b/nl/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From b0194a84bddcbcba32d66ea300267000e1b6a467 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:23:12 +0900 Subject: [PATCH 0483/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 ko/state_of_graphql.yml diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/ko/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From cd078e2e47149d1ca59123a989644bcf83327a8d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:23:25 +0900 Subject: [PATCH 0484/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 pt/state_of_graphql.yml diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/pt/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 5a4f422ad2eda26f51af4944af924073a951b547 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:23:27 +0900 Subject: [PATCH 0485/1932] New translations common.yml (Russian) --- ru/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/ru/common.yml b/ru/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 31bd4601c71ec7d1e3a7f8f1cb56717c8ac6cb03 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:23:34 +0900 Subject: [PATCH 0486/1932] New translations common.yml (Portuguese) --- pt/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/pt/common.yml b/pt/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 9a2fa30a1e5f492bb0c259648591f624b1b99dc1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:23:38 +0900 Subject: [PATCH 0487/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 no/state_of_graphql.yml diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/no/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From ba8d8f6ecaaa88b9ada179430e262a0742bfcdc7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:23:41 +0900 Subject: [PATCH 0488/1932] New translations common.yml (Polish) --- pl/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/pl/common.yml b/pl/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 5de770406e408df14ad423fe5a5f561aa7b90af7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:23:51 +0900 Subject: [PATCH 0489/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 pl/state_of_graphql.yml diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/pl/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 64292969b768da77a314c68b0628fdd24822da9b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:03 +0900 Subject: [PATCH 0490/1932] New translations common.yml (Swedish) --- sv/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/sv/common.yml b/sv/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 287a2760c3d1bea4844e07716cc9c7d3577585f5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:04 +0900 Subject: [PATCH 0491/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 sv/state_of_graphql.yml diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/sv/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 35d6bae469a13d8adc8736b2296def9fb82a72f0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:07 +0900 Subject: [PATCH 0492/1932] New translations common.yml (Turkish) --- tr/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/tr/common.yml b/tr/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 370747a3c8337106af79004eee380964ab3ebe88 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:17 +0900 Subject: [PATCH 0493/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 ru/state_of_graphql.yml diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/ru/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 11f8fc647467cd7d99ab002210cd5a7f39575bff Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:20 +0900 Subject: [PATCH 0494/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/sr/common.yml b/sr/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From 8c82d78e887c4694e5c73e02e1c045c7d24ec9cd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:29 +0900 Subject: [PATCH 0495/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 sr/state_of_graphql.yml diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/sr/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 442565138452bb065abf91a294e52d1f07c8295d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:40 +0900 Subject: [PATCH 0496/1932] New translations state_of_graphql.yml (Chinese Simplified) --- zh/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 zh/state_of_graphql.yml diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/zh/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 47f41075a86f735c9bec65a0b3aa417e86d1414a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:43 +0900 Subject: [PATCH 0497/1932] New translations common.yml (Chinese Traditional) --- zh/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/zh/common.yml b/zh/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From a587f358f4f152ebf6810616cf660e07a5213153 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:53 +0900 Subject: [PATCH 0498/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 tr/state_of_graphql.yml diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/tr/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 54dc4c3cea1ab47ccadcb14f518b157f3f4d215c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:56 +0900 Subject: [PATCH 0499/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/uk/common.yml b/uk/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From c5915e91d3629511662d21c61e9d2b6892d07faf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:24:58 +0900 Subject: [PATCH 0500/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 uk/state_of_graphql.yml diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/uk/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From 9b5b0b1d09703414f983d046263e1ec5704ae7d4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:25:10 +0900 Subject: [PATCH 0501/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/vi/common.yml b/vi/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From ada10d5210496c03b14238c56492a7cd788850cb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:25:20 +0900 Subject: [PATCH 0502/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 vi/state_of_graphql.yml diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/vi/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From fdb7555ad562c3d0bda240614620f1f0092022be Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:25:26 +0900 Subject: [PATCH 0503/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 149 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 en/state_of_graphql.yml diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml new file mode 100644 index 00000000000..f7ec72ab9c2 --- /dev/null +++ b/en/state_of_graphql.yml @@ -0,0 +1,149 @@ +--- +locale: en-US +namespace: graphql +translations: + - + ########################################################################### + #General + ########################################################################### + ########################################################################### + #Sections + ########################################################################### + ########################################################################### + #Options + ########################################################################### + ########################################################################### + #Features + ########################################################################### + #common features + key: features.custom_directives + t: Custom Directives + - + key: features.custom_scalars + t: Custom Scalars + - + key: features.fragments + t: Fragments + - + key: features.unions + t: Unions + - + key: features.interfaces + t: Fragments + - + #directives + key: features.at_skip + t: '@skip' + - + key: features.at_include + t: '@include' + - + key: features.at_deprecated + t: '@deprecated' + - + key: features.at_specified_by + t: '@specifiedBy' + - + key: features.at_defer + t: '@defer' + - + key: features.at_stream + t: '@stream' + - + #security & performance + key: features.persisted_queries + t: Persisted Queries + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_rate_limit + t: Query Rate Limiting + - + key: features.disabling_introspection + t: Disabling Introspection + - + #other features + key: features.graphql_subscriptions + t: GraphQL Subscriptions + - + key: features.federation + t: Federation + - + key: features.schema_stitching + t: Schema Stitching + - + ########################################################################### + #Usage + ########################################################################### + key: usage.graphql_experience + t: GraphQL Experience + - + key: usage.graphql_experience.description + t: How long have you been using GraphQL for? + - + key: usage.usage_type + t: GraphQL Usage Type + - + key: usage.usage_type.description + t: What kind of APIs do you use GraphQL for? + - + key: usage.code_generation_frequency + t: Code Generation Frequency + - + key: usage.code_generation_frequency.description + t: How often do you use code generation tools? + - + key: usage.code_generation_type + t: Code Generation Type + - + key: usage.code_generation_type.description + t: What kind of code generation approach do you tend to favor? + - + key: usage.code_generation_target + t: Code Generation Target + - + key: usage.code_generation_target.description + t: Which part(s) of your codebase do you generate programatically? + - + key: usage.industry_sector + t: Industry Sector + - + key: usage.industry_sector.description + t: Which industry sector are you using GraphQL in? + - + key: usage.server_languages + t: Server Languages + - + key: usage.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.pain_points + t: Main GraphQL Pain Points + - + key: usage.currently_missing + t: Features Currently Missing From GraphQL + - + key: usage.other_tools + t: Other GraphQL Tools + - + key: happiness.state_of_graphql + t: How happy are you with the overall state of the GraphQL ecosystem? + - + ########################################################################### + #Opinions + ########################################################################### + key: opinions.graphql_better_than_rest + t: GraphQL is superior to REST + - + key: opinions.always_prefer_graphql_apis + t: I always prefer working with GraphQL APIs + - + ########################################################################### + #Resources + ########################################################################### + key: resources.first_steps + t: First Steps With GraphQL + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn GraphQL? From a37edb295fb08e33a0fa6e72ac5dee65ab9cafe4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 15:25:35 +0900 Subject: [PATCH 0504/1932] New translations common.yml (English) --- en/common.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/en/common.yml b/en/common.yml index a2c3447fb70..8ccd98d8cd1 100644 --- a/en/common.yml +++ b/en/common.yml @@ -1414,3 +1414,10 @@ translations: key: resources.people.others.description t: > People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? From b726839eb5ae6c80d70461233c6331aacb3bd79c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:05 +0900 Subject: [PATCH 0505/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 0418551ffe01a238ccd0922cc6e1eae7154433ea Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:06 +0900 Subject: [PATCH 0506/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 56c667832d58783eebdf6982a0df2e10b04a5c05 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:07 +0900 Subject: [PATCH 0507/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From bc10001ee05f7375f4bd6b003bff79878623f2b9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:08 +0900 Subject: [PATCH 0508/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From dbe60f3c7c10149c7a6044e42ffc1d3ae0da5b14 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:10 +0900 Subject: [PATCH 0509/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 04f143e78f83431345e18bb465d5cf9ff4290e0a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:12 +0900 Subject: [PATCH 0510/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From bb1b4e12b3ea021c54eae11e5bfcb209ef0bad47 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:13 +0900 Subject: [PATCH 0511/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 84e729bc442680aa241b980a8f750ca228b626cb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:13 +0900 Subject: [PATCH 0512/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 32907e06818ece2a4a1520ef2d221f7753b9ef52 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:14 +0900 Subject: [PATCH 0513/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 0f3228add19cfb989db3e58d242644df4d4b9918 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:15 +0900 Subject: [PATCH 0514/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 4ee78df5a6faba5037c014ceb9fc022966a5b35f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:16 +0900 Subject: [PATCH 0515/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From f933dee0780152002d12eeabbc8e8d2c73dbcd8c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:17 +0900 Subject: [PATCH 0516/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 061c2996a730adbcb0437cb3f94a6302f141de76 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:18 +0900 Subject: [PATCH 0517/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From c7b3392a4d723c24b03ef7b16f1c63fa51ffbab4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:19 +0900 Subject: [PATCH 0518/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 14ef8d25ca767d4e5b0116f97b96440b31129bb3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:20 +0900 Subject: [PATCH 0519/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 1769cca234516764eb80461c40b2639a0e222419 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:21 +0900 Subject: [PATCH 0520/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From a706cf00c59b6c7ee9760d8fe46b004236f12e3d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:22 +0900 Subject: [PATCH 0521/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From db3cee4a5222a7ab5c9fb92d9fcbac62a31d6849 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:23 +0900 Subject: [PATCH 0522/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From af0aad786c8452e3c40c4842f9fb42715503b1fd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:24 +0900 Subject: [PATCH 0523/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 38edf8a81bcf088f9bf2b765d333100696072753 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:25 +0900 Subject: [PATCH 0524/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From c4c3d2e234b5391ea899229bf99f51daa7ce7dc9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:26 +0900 Subject: [PATCH 0525/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From f285481c87757e6b9280cf4ec5040a910273b8bb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:27 +0900 Subject: [PATCH 0526/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 41f058b24f03d7ad06bff4a95d0c5caee2ead5f1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:28 +0900 Subject: [PATCH 0527/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 8388639f511e452a67bf7430997b1f26cff6a3e7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:29 +0900 Subject: [PATCH 0528/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 25ff378b9b1d28c4f3a19a5f4ff94039fc123aeb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:30 +0900 Subject: [PATCH 0529/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 170261d159f3000935c4166c37532c641b70597e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:31 +0900 Subject: [PATCH 0530/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 00d042e7843353709154219a3147429d0b8d1908 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:32 +0900 Subject: [PATCH 0531/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 13d55ffcba8f615a585dbaa5caa8a0d20b5a3fc7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 6 May 2022 16:34:32 +0900 Subject: [PATCH 0532/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 54 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index f7ec72ab9c2..e2cb4f7532e 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -9,6 +9,60 @@ translations: ########################################################################### #Sections ########################################################################### + key: sections.language.title + t: Language + - + key: sections.language.description + t: The vocabulary of GraphQL. + - + key: sections.language.title + t: Directives + - + key: sections.language.description + t: Augmenting your GraphQL fields. + - + key: sections.security_performance.title + t: Security & Performance + - + key: sections.language.description + t: Making your API more robuts. + - + key: sections.graphql_servers.title + t: GraphQL Servers + - + key: sections.graphql_servers.description + t: How you power your API. + - + key: sections.graphql_clients.title + t: GraphQL Clients + - + key: sections.graphql_clients.description + t: Querying your API. + - + key: sections.graphql_api_generators.title + t: GraphQL API Generators + - + key: sections.graphql_api_generators.description + t: Tools and services that create your API for you. + - + key: sections.graphql_code_generators.title + t: GraphQL Code Generators + - + key: sections.graphql_code_generators.description + t: Libraries that write part of your code for you. + - + key: sections.graphql_ides.title + t: GraphQL IDEs + - + key: sections.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: sections.usage.title + t: GraphQL Usage + - + key: sections.usage.description + t: How you use GraphQL. + - ########################################################################### #Options ########################################################################### From 0286ac6d07d03d20cf257c28b73d1d0d162d98ec Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:32 +0900 Subject: [PATCH 0533/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 96effed28f94dca4940da01d3341010fa816c470 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:33 +0900 Subject: [PATCH 0534/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From e6bd1b98cb2e46597135437047ae2772b62fc0b0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:34 +0900 Subject: [PATCH 0535/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From a4bf3b1bf639313cd839ec58fa8738f26e0cadc7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:35 +0900 Subject: [PATCH 0536/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From d8b0f65c23d44e0e0c5527858b91ba11b99ee5a4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:36 +0900 Subject: [PATCH 0537/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From aca629f406693e9628046f49bde810cc569a83fd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:38 +0900 Subject: [PATCH 0538/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 51e4235065645b6a89fbdc78ea42b643e4403064 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:39 +0900 Subject: [PATCH 0539/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 3d2d1b69a3c3f2ae798ad3340c17d1bd5ae5e9fc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:40 +0900 Subject: [PATCH 0540/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 1708799ae43edaf3136c950acc7363e4a33c7cf0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:41 +0900 Subject: [PATCH 0541/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 785d06de8d73a61bfcc83c3406a1c547beb62e82 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:42 +0900 Subject: [PATCH 0542/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From fa1d76bba79f3d143a8e4e6590a2df78c47dbb2d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:43 +0900 Subject: [PATCH 0543/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From fb64efb274ab6f5f10a3d2f49501c2c7f19a8050 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:44 +0900 Subject: [PATCH 0544/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 11cd4c394f4caf7fd0a8feed7bd637a144de1c08 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:45 +0900 Subject: [PATCH 0545/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From f7e13d0977ed509011d4281654062d17ac1985b8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:46 +0900 Subject: [PATCH 0546/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From d9638aa0eef59151ec074865bad6fc8c720d103a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:48 +0900 Subject: [PATCH 0547/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 0483df15fb10919b7af108d317c208a010223022 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:49 +0900 Subject: [PATCH 0548/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From e20e46a92495c44871565e989cfbd4a2b7c3d2af Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:50 +0900 Subject: [PATCH 0549/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 0585b3dcc38681b9d7756ad208317a2d602f0162 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:51 +0900 Subject: [PATCH 0550/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 4da44122ecfaec766c6249283e5ff363d5c72449 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:52 +0900 Subject: [PATCH 0551/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 954fccaf6e8e0a194050415be954fe98a51e2eff Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:53 +0900 Subject: [PATCH 0552/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From d016a25cf5d949f75d4596e44a487286cad9a3c4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:54 +0900 Subject: [PATCH 0553/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From a8fae4ac961b6948c6b92ca93e05194b38c8ae3a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:55 +0900 Subject: [PATCH 0554/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From c01a3f5852c4d154aefa58c95b1eacbeb1d35664 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:56 +0900 Subject: [PATCH 0555/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 15305aaef429f837efb77cb3c8e12f78cac2d862 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:57 +0900 Subject: [PATCH 0556/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From cb5a062895e09b7fd96df6c3d94c6cf3e8cb2f81 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:58 +0900 Subject: [PATCH 0557/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From acca9b1e53d479270b4b832a342232d48adb0b9d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:58:59 +0900 Subject: [PATCH 0558/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From 2126f006ccb486eaad1b553f46c4ca8d50cd1679 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:59:00 +0900 Subject: [PATCH 0559/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From f09cb96250c38059cef37805b7f8dee5878c9801 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 10 May 2022 15:59:01 +0900 Subject: [PATCH 0560/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 333 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 307 insertions(+), 26 deletions(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index e2cb4f7532e..7887536b4ab 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -15,16 +15,16 @@ translations: key: sections.language.description t: The vocabulary of GraphQL. - - key: sections.language.title + key: sections.directives.title t: Directives - - key: sections.language.description + key: sections.directives.description t: Augmenting your GraphQL fields. - key: sections.security_performance.title t: Security & Performance - - key: sections.language.description + key: sections.security_performance.description t: Making your API more robuts. - key: sections.graphql_servers.title @@ -40,13 +40,19 @@ translations: t: Querying your API. - key: sections.graphql_api_generators.title - t: GraphQL API Generators + t: API Generators - key: sections.graphql_api_generators.description t: Tools and services that create your API for you. + - + key: sections.graphql_frameworks.title + t: GraphQL Frameworks + - + key: sections.graphql_frameworks.description + t: Full-stack frameworks that make use of GraphQL. - key: sections.graphql_code_generators.title - t: GraphQL Code Generators + t: Code Generators - key: sections.graphql_code_generators.description t: Libraries that write part of your code for you. @@ -58,14 +64,11 @@ translations: t: Apps and services that help you query your GraphQL API. - key: sections.usage.title - t: GraphQL Usage + t: Usage - key: sections.usage.description t: How you use GraphQL. - - ########################################################################### - #Options - ########################################################################### ########################################################################### #Features ########################################################################### @@ -108,14 +111,47 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_depth_limit - t: Query Depth Limiting + key: features.query_whitelisting + t: Query Whitelisting + - + key: features.query_whitelisting.description + t: Only accept queries from a predefined list. + - + key: features.query_timeouts + t: Query Timeouts - key: features.query_rate_limit t: Query Rate Limiting + - + key: features.query_depth_limit + t: Query Depth Limiting + - + key: features.query_amount_limit + t: Query Amount Limiting + - + key: features.query_amount_limiting.description + t: Put a ceiling on any pagination count passed as a query argument. + - + key: features.query_cost_analysis + t: Query Cost Analysis + - + key: features.query_cost_analysis.description + t: Analyzing a set of factors before deciding whether to allow a query. - key: features.disabling_introspection t: Disabling Introspection + - + key: features.ip_whitelisting + t: IP Whitelisting + - + key: features.ip_whitelisting.description + t: Only allowing a predefined set of IP addresses to access an API. + - + key: features.require_authentication + t: Requiring Authentication + - + key: features.require_authentication.description + t: Require authentication before any API access. - #other features key: features.graphql_subscriptions @@ -136,11 +172,29 @@ translations: key: usage.graphql_experience.description t: How long have you been using GraphQL for? - - key: usage.usage_type - t: GraphQL Usage Type + key: usage.api_type + t: API Types - - key: usage.usage_type.description + key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.client_type + t: API Clients + - + key: usage.client_type.description + t: What kind of clients connect to your APIs? + - + key: usage.data_sources + t: Data Sources + - + key: usage.data_sources.description + t: Which kind of data sources are consumed by your GraphQL APIs? + - + key: usage.security_practices + t: Security Practices + - + key: usage.security_practices.description + t: Which of these practices do you implement in your APIs? - key: usage.code_generation_frequency t: Code Generation Frequency @@ -152,7 +206,7 @@ translations: t: Code Generation Type - key: usage.code_generation_type.description - t: What kind of code generation approach do you tend to favor? + t: If you use code generation, which approaches do you tend to prefer? - key: usage.code_generation_target t: Code Generation Target @@ -161,25 +215,49 @@ translations: t: Which part(s) of your codebase do you generate programatically? - key: usage.industry_sector - t: Industry Sector + t: Industry Sectors - key: usage.industry_sector.description - t: Which industry sector are you using GraphQL in? + t: Which industry sector(s) are you using GraphQL in? + - + key: usage.industry_sector.others + t: Other Industry Sectors - key: usage.server_languages t: Server Languages - key: usage.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? + - + key: usage.server_languages + t: Other Server Languages + - + key: usage.strong_points + t: GraphQL Strong Points + - + key: usage.strong_points.description + t: What are the main reasons why you enjoy using GraphQL? + - + key: usage.strong_points.others + t: Other GraphQL Strong Points - key: usage.pain_points - t: Main GraphQL Pain Points + t: GraphQL Pain Points + - + key: usage.pain_points.description + t: What are your main pain points when using GraphQL? + - + key: usage.pain_points.others + t: Other GraphQL Pain Points - key: usage.currently_missing t: Features Currently Missing From GraphQL - key: usage.other_tools t: Other GraphQL Tools + - + key: usage.other_tools.others + t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -187,17 +265,220 @@ translations: ########################################################################### #Opinions ########################################################################### - key: opinions.graphql_better_than_rest - t: GraphQL is superior to REST - - - key: opinions.always_prefer_graphql_apis - t: I always prefer working with GraphQL APIs - - + #- key: opinions.graphql_better_than_rest + #t: GraphQL is superior to REST + #- key: opinions.always_prefer_graphql_apis + #t: I always prefer working with GraphQL APIs ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_graphql t: First Steps With GraphQL - - key: resources.first_steps.description + key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + ########################################################################### + #Options + ########################################################################### + key: options.graphql_experience.range_less_than_1 + t: Less than one year + - + key: options.graphql_experience.range_1_2 + t: 1 to 2 years + - + key: options.graphql_experience.range_3_5 + t: 3 to 5 years + - + key: options.graphql_experience.range_6_10 + t: 6 to 10 years + - + key: options.graphql_experience.range_more_than_10 + t: More than 10 years + - + key: options.api_type.public_apis + t: Publicly available APIs intended for third-party developers. + - + key: options.api_type.private_apis + t: Private APIs for internal usage. + - + key: options.client_type.browsers + t: Browsers + - + key: options.client_type.mobile_devices + t: Native Mobile Apps + - + key: options.client_type.mobile_devices + t: Native Desktop Apps + - + key: options.client_type.other_servers + t: Other Servers + - + key: options.data_sources.static_files + t: Static files (YAML, Markdown, etc.) + - + key: options.data_sources.databases + t: Databases + - + key: options.data_sources.spreadsheets + t: Spreadsheets + - + key: options.data_sources.cmses + t: CMSes + - + key: options.data_sources.rest_apis + t: REST APIs + - + key: options.data_sources.other_graphql_apis + t: Other GraphQL APIs + - + key: options.code_generation_type.code_first + t: Code-first + - + key: options.code_generation_type.schema_first + t: Schema-first + - + key: options.code_generation_type.database_first + t: Database-first + - + key: options.code_generation_target.graphql_schema + t: GraphQL schema + - + key: options.code_generation_target.non_graphql_typings + t: Non-GraphQL (e.g. TypeScript) typings + - + key: options.code_generation_target.server_resolvers + t: Server resolvers + - + key: options.code_generation_target.fragments_or_queries + t: Client-side fragments and/or queries + - + key: options.code_generation_target.client_code + t: Client-side query code (e.g. React hooks) + - + key: options.strong_points.avoiding_overfetching + t: Avoiding Over-fetching + - + key: options.strong_points.avoiding_overfetching.description + t: Keep API responses smaller by specifying exactly the data you need. + - + key: options.strong_points.introspection + t: Introspection & API Documentation + - + key: options.strong_points.introspection.description + t: Create self-documenting APIs that improve the developer experience. + - + key: options.strong_points.tooling_ecosystem + t: Tooling & Ecosystem + - + key: options.strong_points.tooling_ecosystem.description + t: The different tools, services, and libraries that use GraphQL. + - + key: options.strong_points.type_checking + t: Type-checking + - + key: options.strong_points.type_checking.description + t: Enforcing and validating types for every object in the API. + - + key: options.strong_points.api_aggregation + t: Combining Different APIs + - + key: options.strong_points.api_aggregation.description + t: Being able to combine together different API schemas. + - + key: options.strong_points.aggregating_requests + t: Aggregating Requests + - + key: options.strong_points.aggregating_requests.description + t: Only ever have to make a single request from the client. + - + key: options.strong_points.community + t: Community + - + key: options.strong_points.community.description + t: The people who are active in the GraphQL space. + - + key: options.strong_points.fragment_colocation + t: Fragment Colocation + - + key: options.strong_points.fragment_colocation.description + t: Being able to colocate a component's data requirements next to it. + - + key: options.pain_points.performance + t: Performance + - + key: options.pain_points.performance.description + t: Performance issues such as the n+1 problem. + - + key: options.pain_points.security + t: Security + - + key: options.pain_points.security.description + t: Security issues such as infinitely nested queries. + - + key: options.pain_points.combining_schemas + t: Combining Different Schemas + - + key: options.pain_points.combining_schemas.description + t: Being able to combine together different API schemas. + - + key: options.pain_points.api_versioning + t: API Versioning + - + key: options.pain_points.api_versioning.description + t: Handling deprecated fields and other versioning concerns. + - + key: options.pain_points.file_upload + t: File Upload + - + key: options.pain_points.file_upload.description + t: Being able to upload files through your GraphQL API. + - + key: options.pain_points.testing + t: Testing + - + key: options.pain_points.testing.description + t: Testing your GraphQL API. + - + key: options.pain_points.error_handling + t: Error Handling + - + key: options.pain_points.error_handling.description + t: Returning errors and managing them on the client. + - + key: options.pain_points.client_side_caching + t: Client-side Caching + - + key: options.pain_points.client_side_caching.description + t: Caching data on the client, updating the cache, optimistic UI, etc. + - + #learning methods + key: options.first_steps_graphql.books + t: Books + - + key: options.first_steps_graphql.videos + t: Videos & screencasts + - + key: options.first_steps_graphql.school + t: School & higher education + - + key: options.first_steps_graphql.courses_free + t: Online courses (free) + - + key: options.first_steps_graphql.courses_paid + t: Online courses (paid) + - + key: options.first_steps_graphql.podcasts + t: Podcasts + - + key: options.first_steps_graphql.bootcamp + t: Coding bootcamp + - + key: options.first_steps_graphql.on_the_job + t: On-the-job training + - + key: options.first_steps_graphql.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps_graphql.mentoring + t: Mentoring From a25edb12663078ee5104ae40ece00029f05198e6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:35:54 +0900 Subject: [PATCH 0561/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From c3f37a888ddfc1f92c9e4dd1c08a6ec5205bcb9b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:35:55 +0900 Subject: [PATCH 0562/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 79044eedf72eaa36dc48f41cfe5689e99d4bed0f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:35:56 +0900 Subject: [PATCH 0563/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From c4917a0c7541884f9b7382deadd87f862d67786d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:35:57 +0900 Subject: [PATCH 0564/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 67e0c689bfe2a2e3735f792a29e89ca9b5676745 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:35:58 +0900 Subject: [PATCH 0565/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 0b6c5d2009ddfc8703a9cd1a918c6a9f118183da Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:01 +0900 Subject: [PATCH 0566/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From ea512ea5f1486606822d3b8ce54cd0288780483e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:02 +0900 Subject: [PATCH 0567/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From d7c6b589c1664d677fdafe4d9c4b19fc4299935e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:03 +0900 Subject: [PATCH 0568/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 3092714b32dd66c99270a5adfc48734b80523ee1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:04 +0900 Subject: [PATCH 0569/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From c0841b55559350996c0a414dbaae5526b1efe706 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:05 +0900 Subject: [PATCH 0570/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 1991d7a1724ac137b7ade5987f7d29e4da62f3df Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:06 +0900 Subject: [PATCH 0571/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 6154207f56457f052274d86597e0b78f5423341d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:07 +0900 Subject: [PATCH 0572/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From fac76724dadd1f2f273b9b30dafd7d5946fffe23 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:08 +0900 Subject: [PATCH 0573/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 66e2f9d0fcb84ac4ad51cf08e35bde64ca214bc3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:09 +0900 Subject: [PATCH 0574/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From def7aabd1812f59f6f2a4bc7c348bb24cefd0ec2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:10 +0900 Subject: [PATCH 0575/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 79eea7d255435998820f3d5081e29c71289a4aac Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:11 +0900 Subject: [PATCH 0576/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 0770c7a022f0663bd5a2323c6855d013b1ab1e49 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:12 +0900 Subject: [PATCH 0577/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 76fe5e3feb44b34325dd67bdc3f1c9bd4f80ef1c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:13 +0900 Subject: [PATCH 0578/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 4da87784f597e3cce8176164a701bc7518842971 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:14 +0900 Subject: [PATCH 0579/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 06a60afd7d0f3a3e17d2ff8772901ee5cccddcc9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:15 +0900 Subject: [PATCH 0580/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 3e56ec01097af1684e4ace79e9dfd6d5aa26918a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:16 +0900 Subject: [PATCH 0581/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From af01cff94cff90627c6cc3bbbe0150833e02a51b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:17 +0900 Subject: [PATCH 0582/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 86d221870a62dc2f386a7571f88757e3df06f241 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:18 +0900 Subject: [PATCH 0583/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From cfa6d7af13a2e37c398953ebe3b3710591b033db Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:19 +0900 Subject: [PATCH 0584/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From b0f75bb8b3840e3dc3669fae2a9cc20a18754f4a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:20 +0900 Subject: [PATCH 0585/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From c8a48a547d0c987a338598a986d9ede73848d837 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:21 +0900 Subject: [PATCH 0586/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From c9f53360dd94f5f9badb8b2e883501d808dbde2f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:22 +0900 Subject: [PATCH 0587/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From 3152ca6d0efb354cf4583b2aff5243454ed2c2b2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 13:36:23 +0900 Subject: [PATCH 0588/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 174 +++++++++++++++++++++++++++------------- 1 file changed, 117 insertions(+), 57 deletions(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index 7887536b4ab..5d6f9636975 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -43,28 +43,28 @@ translations: t: API Generators - key: sections.graphql_api_generators.description - t: Tools and services that create your API for you. + t: ORMs, CMSes, and other tools that create an API for you. - - key: sections.graphql_frameworks.title - t: GraphQL Frameworks + key: sections.web_frameworks.title + t: Web Frameworks - - key: sections.graphql_frameworks.description - t: Full-stack frameworks that make use of GraphQL. + key: sections.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. - key: sections.graphql_code_generators.title - t: Code Generators + t: Code & Schema Generators - key: sections.graphql_code_generators.description - t: Libraries that write part of your code for you. + t: Generators, schema builders, and other libraries that write part of your code for you. - - key: sections.graphql_ides.title - t: GraphQL IDEs + key: sections.schema_builders.title + t: Schema Builders - - key: sections.graphql_ides.description - t: Apps and services that help you query your GraphQL API. + key: sections.schema_builders.description + t: Libraries and utilities that help you build all or part of your GraphQL schema. - key: sections.usage.title - t: Usage + t: GraphQL Usage - key: sections.usage.description t: How you use GraphQL. @@ -111,10 +111,10 @@ translations: key: features.persisted_queries t: Persisted Queries - - key: features.query_whitelisting - t: Query Whitelisting + key: features.query_allowlisting + t: Query Allow-listing - - key: features.query_whitelisting.description + key: features.query_allowlisting.description t: Only accept queries from a predefined list. - key: features.query_timeouts @@ -141,10 +141,10 @@ translations: key: features.disabling_introspection t: Disabling Introspection - - key: features.ip_whitelisting - t: IP Whitelisting + key: features.ip_allowlisting + t: IP Allow-listing - - key: features.ip_whitelisting.description + key: features.ip_allowlisting.description t: Only allowing a predefined set of IP addresses to access an API. - key: features.require_authentication @@ -157,11 +157,80 @@ translations: key: features.graphql_subscriptions t: GraphQL Subscriptions - - key: features.federation - t: Federation + key: features.live_queries + t: Live Queries + - + key: features.apollo_federation + t: Apollo Federation - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Other Tools + ########################################################################### + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages.others + t: Other server languages + - + key: other_tools.combining_schemas + t: Combining Schemas + - + key: other_tools.combining_schemas.description + t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? + - + key: other_tools.combining_schemas.others + t: Other tools for combining schemas + - + key: other_tools.server_languages + t: Server Languages + - + key: other_tools.server_languages.description + t: Which language(s) do you use to write your GraphQL back-ends? + - + key: other_tools.server_languages + t: Other Server Languages + - + key: other_tools.graphql_ides + t: GraphQL IDEs + - + key: other_tools.graphql_ides.description + t: Apps and services that help you query your GraphQL API. + - + key: other_tools.graphql_ides.others + t: Other GraphQL IDEs + - + key: other_tools.web_frameworks + t: Web Frameworks + - + key: other_tools.web_frameworks.description + t: Web frameworks that you use in conjunction with GraphQL. + - + key: other_tools.web_frameworks.others + t: Other web frameworks + - + key: other_tools.databases + t: Databases + - + key: other_tools.databases.description + t: Which databases do you use in conjunction with GraphQL? + - + key: other_tools.databases.others + t: Other databases + - + key: other_tools.other_tools + t: Other GraphQL Tools + - + key: other_tools.other_tools.description + t: Other tools, libraries, or services you use + - + key: other_tools.other_tools.others + t: Other GraphQL tools not previously mentioned - ########################################################################### #Usage @@ -177,12 +246,18 @@ translations: - key: usage.api_type.description t: What kind of APIs do you use GraphQL for? + - + key: usage.api_type.others + t: Other kind of APIs - key: usage.client_type t: API Clients - key: usage.client_type.description t: What kind of clients connect to your APIs? + - + key: usage.client_type.others + t: Other types of clients - key: usage.data_sources t: Data Sources @@ -190,29 +265,26 @@ translations: key: usage.data_sources.description t: Which kind of data sources are consumed by your GraphQL APIs? - - key: usage.security_practices - t: Security Practices - - - key: usage.security_practices.description - t: Which of these practices do you implement in your APIs? - - - key: usage.code_generation_frequency - t: Code Generation Frequency - - - key: usage.code_generation_frequency.description - t: How often do you use code generation tools? + key: usage.data_sources.others + t: Other data sources - key: usage.code_generation_type t: Code Generation Type - key: usage.code_generation_type.description t: If you use code generation, which approaches do you tend to prefer? + - + key: usage.code_generation_type.others + t: Other types of code generation - key: usage.code_generation_target t: Code Generation Target - key: usage.code_generation_target.description t: Which part(s) of your codebase do you generate programatically? + - + key: usage.code_generation_target.others + t: Other code generation targets - key: usage.industry_sector t: Industry Sectors @@ -222,15 +294,6 @@ translations: - key: usage.industry_sector.others t: Other Industry Sectors - - - key: usage.server_languages - t: Server Languages - - - key: usage.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: usage.server_languages - t: Other Server Languages - key: usage.strong_points t: GraphQL Strong Points @@ -249,15 +312,6 @@ translations: - key: usage.pain_points.others t: Other GraphQL Pain Points - - - key: usage.currently_missing - t: Features Currently Missing From GraphQL - - - key: usage.other_tools - t: Other GraphQL Tools - - - key: usage.other_tools.others - t: Other GraphQL Tools - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? @@ -297,10 +351,13 @@ translations: t: More than 10 years - key: options.api_type.public_apis - t: Publicly available APIs intended for third-party developers. + t: Publicly-available APIs intended for third-party developers + - + key: options.api_type.personal_apis + t: Exposed APIs intended for your own website and/or apps - key: options.api_type.private_apis - t: Private APIs for internal usage. + t: Private, unexposed APIs for internal usage - key: options.client_type.browsers t: Browsers @@ -308,7 +365,7 @@ translations: key: options.client_type.mobile_devices t: Native Mobile Apps - - key: options.client_type.mobile_devices + key: options.client_type.desktop_apps t: Native Desktop Apps - key: options.client_type.other_servers @@ -327,22 +384,25 @@ translations: t: CMSes - key: options.data_sources.rest_apis - t: REST APIs + t: REST APIs (Swagger/OpenAPI, json-schema, oData, etc.) - key: options.data_sources.other_graphql_apis t: Other GraphQL APIs + - + key: options.data_sources.other_api_protocols + t: Other API Protocols (gRPC, SOAP, Apache Thrift, etc.) - key: options.code_generation_type.code_first - t: Code-first + t: Code-first (JS, TS, JSON, etc.) - key: options.code_generation_type.schema_first - t: Schema-first + t: Schema-first (GraphQL SDL-first) - key: options.code_generation_type.database_first t: Database-first - key: options.code_generation_target.graphql_schema - t: GraphQL schema + t: GraphQL schema (SDL) - key: options.code_generation_target.non_graphql_typings t: Non-GraphQL (e.g. TypeScript) typings @@ -354,7 +414,7 @@ translations: t: Client-side fragments and/or queries - key: options.code_generation_target.client_code - t: Client-side query code (e.g. React hooks) + t: Other client-side code (e.g. React hooks) - key: options.strong_points.avoiding_overfetching t: Avoiding Over-fetching From d68297488f47ef61e453341ceb90425a55088329 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:07 +0900 Subject: [PATCH 0589/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 912f5fcc832a15a79d6b0d6a2e9734d18c8d129c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:08 +0900 Subject: [PATCH 0590/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 67eabf59b907eb5e84ed61d99efe42e467d65913 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:09 +0900 Subject: [PATCH 0591/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From ba5c35ef185aeaada0f5bb79d695cba1412f280f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:10 +0900 Subject: [PATCH 0592/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 3cc088b8d30a99b079106c63e1e5607eb8a60128 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:11 +0900 Subject: [PATCH 0593/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 28d61a006cf7460d320d29d780a48316a980221a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:13 +0900 Subject: [PATCH 0594/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 7ed074a2de8dd59ce7276f45b28768b8ea3e4dd6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:14 +0900 Subject: [PATCH 0595/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From b085ba7e036764c9792c3b31c2a1539d477326b1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:15 +0900 Subject: [PATCH 0596/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 132a3ecacc59701e2b7c2a439b58761c0987e827 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:16 +0900 Subject: [PATCH 0597/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 287c3c7c86578311d1b8171d12da748e5edeab54 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:17 +0900 Subject: [PATCH 0598/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 6b137e0696c2af7609a5a3dffcc654eec1185d7a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:18 +0900 Subject: [PATCH 0599/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 8882e0cdac4434ab83b4ca744de1b2a5ddde716c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:19 +0900 Subject: [PATCH 0600/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From f97ac580615a5543f9c9fab8c49cb2cd95d86984 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:20 +0900 Subject: [PATCH 0601/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 52c56938d44a30b8f4637c6d3045d3384a190c6b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:21 +0900 Subject: [PATCH 0602/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 9eb2aae0ed242ac6eb001a5ca38d76d5cb0bf8db Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:22 +0900 Subject: [PATCH 0603/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 5e70613a916896d2d7476889d94eeb17fad861e5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:23 +0900 Subject: [PATCH 0604/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From f6bb981184109df952c1deb39fd3c44e1c2506c1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:24 +0900 Subject: [PATCH 0605/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 1e351513f3570cf2614a2959bba594d07bb7f096 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:25 +0900 Subject: [PATCH 0606/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 8613930fdb190daf180f7a53da642e6650166b4c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:26 +0900 Subject: [PATCH 0607/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 8f48423401c62c8fe2735d9eda293c2d05105e4e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:27 +0900 Subject: [PATCH 0608/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 2dd4ed685df3202c3af35de603cb3a7cc56b7a95 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:28 +0900 Subject: [PATCH 0609/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From cb944c8627aebcecad4ab139883a5ab3756f159c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:29 +0900 Subject: [PATCH 0610/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 13b9ff5f431a287231865b6efd67828d5a621661 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:30 +0900 Subject: [PATCH 0611/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 1ce1de98efcb634c98ece6a9f2b7ffaf0376785d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:31 +0900 Subject: [PATCH 0612/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From fe121e016fef1055bf3b297eea2b934d1b74ef53 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:32 +0900 Subject: [PATCH 0613/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 658b6f11c644b1d7f99b38ffcdc42a37c93bd896 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:33 +0900 Subject: [PATCH 0614/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 832d1838e24d93bd915450a05e3c6d640dd04529 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:34 +0900 Subject: [PATCH 0615/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From d7361c4ba930cfeb1d4b3920cc9bad83614116d1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 19 May 2022 14:56:35 +0900 Subject: [PATCH 0616/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index 5d6f9636975..b4f08454fff 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -6,6 +6,17 @@ translations: ########################################################################### #General ########################################################################### + ########################################################################### + #Survey + ########################################################################### + key: features.features_intro + t: > + Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! + - + key: tools.tools_intro + t: > + The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - ########################################################################### #Sections ########################################################################### @@ -86,7 +97,7 @@ translations: t: Unions - key: features.interfaces - t: Fragments + t: Interfaces - #directives key: features.at_skip From 5699c096fce8c7d79092e338e71306f4e62876e2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:16 +0900 Subject: [PATCH 0617/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 9c3aa3601e64e0a35aac5b39982aa51d5a4da1e1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:17 +0900 Subject: [PATCH 0618/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 8372ee60d7dab21770f6fbe22aa81d551eac9e4e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:18 +0900 Subject: [PATCH 0619/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 0c440705bd4952e35958a716faa80c6cbb1c4d04 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:20 +0900 Subject: [PATCH 0620/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From fcd7ed1203fd939ac62a16cc9f17934e8cfe4f62 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:21 +0900 Subject: [PATCH 0621/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 2c88c08257a88002173afe36d6ffe0bc282e3e97 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:23 +0900 Subject: [PATCH 0622/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 054fa7807af592654fcf7bc46401eda43c5a4fd2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:24 +0900 Subject: [PATCH 0623/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From a2687cf2fee5c157e65b993994408d28b4630d10 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:26 +0900 Subject: [PATCH 0624/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 56311bb18c4da6e7c47529b74747af9bfefa1b32 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:27 +0900 Subject: [PATCH 0625/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 2a0ea9bbf245bcfdf1c0232e6a9fdc4c650c29a9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:28 +0900 Subject: [PATCH 0626/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 24796423ff4211643a5c1a7c89a161005b7a8901 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:29 +0900 Subject: [PATCH 0627/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 126ecbdeee3f33e772ba43ad975690bc17919b50 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:30 +0900 Subject: [PATCH 0628/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 59f38555d2a2fa63bf442d0609cec1a712b86fec Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:31 +0900 Subject: [PATCH 0629/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From fb1c9f41c49fffdfcab9cf84c36425d8a9dcf155 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:31 +0900 Subject: [PATCH 0630/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 95c88609a3790965981a66d2648c7c7b964dd224 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:32 +0900 Subject: [PATCH 0631/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From a20b1246d1581325988181dace2f5225245c2f91 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:34 +0900 Subject: [PATCH 0632/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From b48750906c5fa119c871cb779a4a2e8c0ba802c6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:35 +0900 Subject: [PATCH 0633/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 98f44ac67dbe10fc4fcd6eaca4de57fa7f8042b9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:36 +0900 Subject: [PATCH 0634/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From a31ce04c22790cbf4296bee73a6329c80d761d9d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:37 +0900 Subject: [PATCH 0635/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From af5c799f304a34a7d4a4a6a396dc1dec40398b72 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:38 +0900 Subject: [PATCH 0636/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 84c3b67f30c6f4f7abe9901935490a6dc161a80c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:39 +0900 Subject: [PATCH 0637/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 0ae25528445b3a514ce16c4471424b0e4ecf0909 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:40 +0900 Subject: [PATCH 0638/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 91c96d7341af1058e7b34038f52a83dbeebeae3b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:41 +0900 Subject: [PATCH 0639/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 4aaaaebc437d656a51de42764c33ba1d0acadb81 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:42 +0900 Subject: [PATCH 0640/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From ca9f1590d1c4c5835454f2a79399ed55a5feac83 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:43 +0900 Subject: [PATCH 0641/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 5fceead5c107f0f9c0adc314ff43c4c9eece2cce Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:44 +0900 Subject: [PATCH 0642/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 30f58d5298962a3c34371c6bc7b89e4dcfb663f5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:45 +0900 Subject: [PATCH 0643/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 191b7335eab39807600346a0fa8f30ef8f27614c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 20 May 2022 07:32:46 +0900 Subject: [PATCH 0644/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index b4f08454fff..00c053449f1 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -20,10 +20,10 @@ translations: ########################################################################### #Sections ########################################################################### - key: sections.language.title + key: sections.graphql_language.title t: Language - - key: sections.language.description + key: sections.graphql_language.description t: The vocabulary of GraphQL. - key: sections.directives.title From 83fee8e8e4847cc888fd07e493b93c6c448bd699 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:41 +0900 Subject: [PATCH 0645/1932] New translations common.yml (Romanian) --- ro/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/ro/common.yml b/ro/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 6cc2c1ceb3229211d896e312ce779b12c0734c6e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:42 +0900 Subject: [PATCH 0646/1932] New translations surveys.yml (Hungarian) --- hu/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/hu/surveys.yml b/hu/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/hu/surveys.yml +++ b/hu/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From c41af8493530a9fff540fb30b03350ec73e01f66 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:43 +0900 Subject: [PATCH 0647/1932] New translations surveys.yml (Greek) --- el/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/el/surveys.yml b/el/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/el/surveys.yml +++ b/el/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From d53af1263b06371c7030ce61f06a0f3917478b38 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:44 +0900 Subject: [PATCH 0648/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 9568bd327a530fef6742c8809c4450912e0e7001 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:45 +0900 Subject: [PATCH 0649/1932] New translations common.yml (Finnish) --- fi/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/fi/common.yml b/fi/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 90a1694faa2b642f7e69043fc45028914e9a8805 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:46 +0900 Subject: [PATCH 0650/1932] New translations surveys.yml (Finnish) --- fi/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/fi/surveys.yml b/fi/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/fi/surveys.yml +++ b/fi/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From f0a31a4fc30bc2b4601cbcb49cb683e323f244ed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:47 +0900 Subject: [PATCH 0651/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 2554c1fc9f557a4546cb1d8ba744469b00abd8fd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:48 +0900 Subject: [PATCH 0652/1932] New translations common.yml (Hebrew) --- he/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/he/common.yml b/he/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/he/common.yml +++ b/he/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From c827e9a4e996f994c5e10455e2afbdb1286a3622 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:49 +0900 Subject: [PATCH 0653/1932] New translations surveys.yml (Hebrew) --- he/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/he/surveys.yml b/he/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/he/surveys.yml +++ b/he/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 8413857f9bcb07afc1f2b4528d9319245664555f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:50 +0900 Subject: [PATCH 0654/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 243afc376e62f8fed37b9932b16009b46f622e43 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:51 +0900 Subject: [PATCH 0655/1932] New translations common.yml (Hungarian) --- hu/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/hu/common.yml b/hu/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 70f10b3b2254a7589f7a89ed80a68951ba5b36ab Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:52 +0900 Subject: [PATCH 0656/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From f3740a5bd19345cb95189215d51a777703e0bd81 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:53 +0900 Subject: [PATCH 0657/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 0f4ccc958bf3bcd57e0cb21b33e5b888285c04ad Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:54 +0900 Subject: [PATCH 0658/1932] New translations common.yml (Italian) --- it/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/it/common.yml b/it/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/it/common.yml +++ b/it/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 46707d5f801190a668312806e1a2dba3776e24e3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:55 +0900 Subject: [PATCH 0659/1932] New translations surveys.yml (Italian) --- it/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/it/surveys.yml b/it/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/it/surveys.yml +++ b/it/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 3682b05990d1bbce412e1a6e8a4e5329379dcf77 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:56 +0900 Subject: [PATCH 0660/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 11a3eba60a8669f6e1bf310bfcb504c4220d45e6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:57 +0900 Subject: [PATCH 0661/1932] New translations common.yml (Japanese) --- ja/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/ja/common.yml b/ja/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 246766ec154de759fd52afa711777e279737f3a1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:58 +0900 Subject: [PATCH 0662/1932] New translations surveys.yml (Japanese) --- ja/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/ja/surveys.yml b/ja/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/ja/surveys.yml +++ b/ja/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 4cfdecd72e84892a098d43c1432350afa559ae7e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:39:59 +0900 Subject: [PATCH 0663/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From ed0f535b3e15ab73f422f157768f0ab909006be2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:01 +0900 Subject: [PATCH 0664/1932] New translations common.yml (Korean) --- ko/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/ko/common.yml b/ko/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 76818316d58a9bf9068a692f5c6a1c85eff56e69 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:03 +0900 Subject: [PATCH 0665/1932] New translations surveys.yml (Korean) --- ko/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/ko/surveys.yml b/ko/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/ko/surveys.yml +++ b/ko/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From e4f64480fe59d2968bccb8ae3a5c4c63bf360291 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:04 +0900 Subject: [PATCH 0666/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 630302b065675bbad48a790e26d880ca90754abe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:05 +0900 Subject: [PATCH 0667/1932] New translations common.yml (Dutch) --- nl/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/nl/common.yml b/nl/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From d89ef6fae9bbf612a26ff580684c4da9036a17b4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:06 +0900 Subject: [PATCH 0668/1932] New translations common.yml (Greek) --- el/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/el/common.yml b/el/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/el/common.yml +++ b/el/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 1253abff7d7126f27a6009b3154c9da8d9ca4883 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:07 +0900 Subject: [PATCH 0669/1932] New translations surveys.yml (German) --- de/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/de/surveys.yml b/de/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/de/surveys.yml +++ b/de/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 9f5a8ba96e12c4a7a2bc0ca4f5b830c53b73ae3f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:08 +0900 Subject: [PATCH 0670/1932] New translations surveys.yml (Romanian) --- ro/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/ro/surveys.yml b/ro/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/ro/surveys.yml +++ b/ro/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From a4eccad08195c6715cf17a89025ec92085fa4ebf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:09 +0900 Subject: [PATCH 0671/1932] New translations common.yml (Arabic) --- ar/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/ar/common.yml b/ar/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 16dac17b086f8d11cc47b3de3843c4971e1e28f4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:10 +0900 Subject: [PATCH 0672/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 52d75d76d8f0442e6f75107f296757f03ec7fa2c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:11 +0900 Subject: [PATCH 0673/1932] New translations common.yml (French) --- fr/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/fr/common.yml b/fr/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From bc16b1c4ba828a08ba8b02b6235d240ba2b2fb12 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:12 +0900 Subject: [PATCH 0674/1932] New translations surveys.yml (French) --- fr/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/fr/surveys.yml b/fr/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/fr/surveys.yml +++ b/fr/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 06c0a64ca69c7a28d393ea22069597a38728a1ac Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:13 +0900 Subject: [PATCH 0675/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 733ed2f267a2fa2649ab49a67f24e877524bb484 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:14 +0900 Subject: [PATCH 0676/1932] New translations common.yml (Spanish) --- es/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/es/common.yml b/es/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/es/common.yml +++ b/es/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From e939af99c48df95c1357fc4230461eaa48e05395 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:15 +0900 Subject: [PATCH 0677/1932] New translations surveys.yml (Spanish) --- es/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/es/surveys.yml b/es/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/es/surveys.yml +++ b/es/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 921e6b9d2b6bd113dad4e8e8ad2d99108be18956 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:16 +0900 Subject: [PATCH 0678/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From c85955aab1bc890f0f944da0ac778d6556c7fbdd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:17 +0900 Subject: [PATCH 0679/1932] New translations common.yml (Afrikaans) --- af/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/af/common.yml b/af/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/af/common.yml +++ b/af/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 0ec2b293770213a42165092b778bc15eaa2fea18 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:18 +0900 Subject: [PATCH 0680/1932] New translations surveys.yml (Afrikaans) --- af/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/af/surveys.yml b/af/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/af/surveys.yml +++ b/af/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From a128bf11e2afb7948c53d6d84b00e2aedfec21a8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:19 +0900 Subject: [PATCH 0681/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 7f1236d3fc7b73a8aae39f2c966bf4d82f22b1ab Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:20 +0900 Subject: [PATCH 0682/1932] New translations surveys.yml (Arabic) --- ar/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/ar/surveys.yml b/ar/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/ar/surveys.yml +++ b/ar/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 79d393e804bec28868f9c9447d0ae9512f1e1e84 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:21 +0900 Subject: [PATCH 0683/1932] New translations common.yml (German) --- de/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/de/common.yml b/de/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/de/common.yml +++ b/de/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 29ce4848a3559dcb5d98bb1ee99ac1618624eead Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:22 +0900 Subject: [PATCH 0684/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From fe68b6d3b62c72ddaa87734ea2defd1d682a7547 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:23 +0900 Subject: [PATCH 0685/1932] New translations common.yml (Catalan) --- ca/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/ca/common.yml b/ca/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 719b2db06e3109df702b341cb03e29fe37d4f81c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:24 +0900 Subject: [PATCH 0686/1932] New translations surveys.yml (Catalan) --- ca/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/ca/surveys.yml b/ca/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/ca/surveys.yml +++ b/ca/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 4762d042a671d8cc33e5a46106c78e43cfb6f2a5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:25 +0900 Subject: [PATCH 0687/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 44bbf8fb0353d44ac8d8ee55f007b6860765b0e7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:26 +0900 Subject: [PATCH 0688/1932] New translations common.yml (Czech) --- cs/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/cs/common.yml b/cs/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 43248ec182ad3b17237608ca2aabd78a07df7545 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:27 +0900 Subject: [PATCH 0689/1932] New translations surveys.yml (Czech) --- cs/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/cs/surveys.yml b/cs/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/cs/surveys.yml +++ b/cs/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From a4ec3fe6446cdd7cb0c313cda69811de7c15f4f3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:28 +0900 Subject: [PATCH 0690/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From f98728a3ad8e82ba06e961ebd2151dd7a6d180f6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:29 +0900 Subject: [PATCH 0691/1932] New translations common.yml (Danish) --- da/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/da/common.yml b/da/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/da/common.yml +++ b/da/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From d6c7b69a3e6a7244db8f4c8522ef205dcb990ca9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:30 +0900 Subject: [PATCH 0692/1932] New translations surveys.yml (Danish) --- da/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/da/surveys.yml b/da/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/da/surveys.yml +++ b/da/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From af15e51ca53bf5b2893fb8b2d60b7d4f711b334b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:31 +0900 Subject: [PATCH 0693/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From e237988355cb77ed26d109652d4713f52f2275ab Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:32 +0900 Subject: [PATCH 0694/1932] New translations surveys.yml (Dutch) --- nl/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/nl/surveys.yml b/nl/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/nl/surveys.yml +++ b/nl/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From da3e96d8672e826b893b4c621e4d3e64bcc47bc7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:33 +0900 Subject: [PATCH 0695/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 9a9f1b602d3d29352cf201e5db5267e4f7b4ee1a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:34 +0900 Subject: [PATCH 0696/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 217db4a0777e6c92509b1a8aa9715c98fd963697 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:35 +0900 Subject: [PATCH 0697/1932] New translations surveys.yml (Ukrainian) --- uk/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/uk/surveys.yml b/uk/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/uk/surveys.yml +++ b/uk/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 42b7b035ded2d6610df2ed5870bf8dbad00a7eb5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:36 +0900 Subject: [PATCH 0698/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 5fa197d0b882947c92ab089e618d93de45fbb59c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:37 +0900 Subject: [PATCH 0699/1932] New translations common.yml (Chinese Simplified) --- zh/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/zh/common.yml b/zh/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 0708b944787f5f087b1caea9f93c4903a5eb7017 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:38 +0900 Subject: [PATCH 0700/1932] New translations surveys.yml (Chinese Simplified) --- zh/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/zh/surveys.yml b/zh/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/zh/surveys.yml +++ b/zh/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 0639e9070d875d25c7e0a3fb87210a96d0e8f2f0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:41 +0900 Subject: [PATCH 0701/1932] New translations common.yml (English) --- en/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/en/common.yml b/en/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/en/common.yml +++ b/en/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From ee6b1760722f6d97fa412622ebeae02fe0ded7cb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:42 +0900 Subject: [PATCH 0702/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From e42cdf01e275a5e34bcfcc23f7cdd5d528feafc1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:43 +0900 Subject: [PATCH 0703/1932] New translations surveys.yml (English) --- en/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/en/surveys.yml b/en/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/en/surveys.yml +++ b/en/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From e185255839a8d0a18e98f2cfdfbe69e302d3abcd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:44 +0900 Subject: [PATCH 0704/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From b63eaab5bf6ad4502b27246dc7085692688a2807 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:45 +0900 Subject: [PATCH 0705/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/vi/common.yml b/vi/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From e19a2f9c0fbea9368fa14c54b432fe563142625d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:46 +0900 Subject: [PATCH 0706/1932] New translations surveys.yml (Vietnamese) --- vi/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/vi/surveys.yml b/vi/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/vi/surveys.yml +++ b/vi/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 512b018e6a79da4c3827305190ad1baeb75db34f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:47 +0900 Subject: [PATCH 0707/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 265ae588a27afb2ed103740367810f251b03dbd1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:48 +0900 Subject: [PATCH 0708/1932] New translations common.yml (Portuguese, Brazilian) --- pt/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/pt/common.yml b/pt/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 66402e778c89b4ce388878442adda2177f43024e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:49 +0900 Subject: [PATCH 0709/1932] New translations surveys.yml (Portuguese, Brazilian) --- pt/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/pt/surveys.yml b/pt/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/pt/surveys.yml +++ b/pt/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From dd3b548cc0959fe5b1173370663989eb4ee12aaa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:50 +0900 Subject: [PATCH 0710/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/uk/common.yml b/uk/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 3bd2859f039a1f8ee81a882f7382696ee90953ea Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:51 +0900 Subject: [PATCH 0711/1932] New translations surveys.yml (Turkish) --- tr/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/tr/surveys.yml b/tr/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/tr/surveys.yml +++ b/tr/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 7cded20aa4501cdb58d0731e63f308ea7aa176e3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:52 +0900 Subject: [PATCH 0712/1932] New translations common.yml (Norwegian) --- no/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/no/common.yml b/no/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/no/common.yml +++ b/no/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 7fb818b4a3f5abfb9eb915b8fb1f802327daaf6c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:53 +0900 Subject: [PATCH 0713/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From a8a32ec90a0db6e21a7d325f461f440d9de27699 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:54 +0900 Subject: [PATCH 0714/1932] New translations surveys.yml (Norwegian) --- no/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/no/surveys.yml b/no/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/no/surveys.yml +++ b/no/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From cd8eb72fbe29f7b2bc69f827b4ee6e64d4e83adb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:54 +0900 Subject: [PATCH 0715/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 82d1f2e0b5d74a5841cb373ae865436cb870a515 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:56 +0900 Subject: [PATCH 0716/1932] New translations common.yml (Polish) --- pl/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/pl/common.yml b/pl/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 84c549e9f9a5d92ee1dd6fded568d3f6449c2f2a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:56 +0900 Subject: [PATCH 0717/1932] New translations surveys.yml (Polish) --- pl/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/pl/surveys.yml b/pl/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/pl/surveys.yml +++ b/pl/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 530b2872dc7b5f712ddda874bbfce666f4032a3d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:40:57 +0900 Subject: [PATCH 0718/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From b5341157e742a59418da9ea7bceb7433900959ba Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:41:01 +0900 Subject: [PATCH 0719/1932] New translations common.yml (Russian) --- ru/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/ru/common.yml b/ru/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From bfbbb812ec4d908b7e3a2cdfab60bce6480442fb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:41:05 +0900 Subject: [PATCH 0720/1932] New translations common.yml (Turkish) --- tr/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/tr/common.yml b/tr/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 5c2eee89d567f379256c89612178a128bd5b820e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:41:06 +0900 Subject: [PATCH 0721/1932] New translations surveys.yml (Russian) --- ru/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/ru/surveys.yml b/ru/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/ru/surveys.yml +++ b/ru/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 49164217eb9d9e01ff7c8d9ec6a4179270ab8c97 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:41:07 +0900 Subject: [PATCH 0722/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From 917407ec0c8c52696119312bc7c09ea05226e0f3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:41:08 +0900 Subject: [PATCH 0723/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/sr/common.yml b/sr/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From b8c6bb3d3a197cf99bd2cff593b536b47e558c69 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:41:09 +0900 Subject: [PATCH 0724/1932] New translations surveys.yml (Serbian (Cyrillic)) --- sr/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/sr/surveys.yml b/sr/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/sr/surveys.yml +++ b/sr/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From 979c9880ed24b5e6f32228a1f07abd5c5188194d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:41:10 +0900 Subject: [PATCH 0725/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From f7a0c45f8d5bde984b27577adc60253a4f7cea80 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:41:11 +0900 Subject: [PATCH 0726/1932] New translations common.yml (Swedish) --- sv/common.yml | 62 +++++++++++++++++++++++++-------------------------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/sv/common.yml b/sv/common.yml index 8ccd98d8cd1..6cb7380b7d8 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -424,50 +424,50 @@ translations: - #age key: options.age.range_less_than_10 - t: Under 10 years old + t: 10 years old or under - key: options.age.range_10_18 - t: 10-18 years old + t: 11-18 years old - key: options.age.range_18_24 - t: 18-24 years old + t: 19-24 years old - key: options.age.range_25_34 - t: 24-34 years old + t: 25-34 years old - key: options.age.range_35_44 - t: 35-44 years old + t: 36-44 years old - key: options.age.range_45_54 - t: 45-54 years old + t: 46-54 years old - key: options.age.range_55_64 - t: 55-64 years old + t: 56-64 years old - key: options.age.range_more_than_65 t: 65 years or older - #age (short versions) key: options.age.range_less_than_10.short - t: '<10' + t: '<=10' - key: options.age.range_10_18.short - t: 10-18 + t: 11-18 - key: options.age.range_18_24.short - t: 18-24 + t: 19-24 - key: options.age.range_25_34.short - t: 24-34 + t: 25-34 - key: options.age.range_35_44.short - t: 35-44 + t: 36-44 - key: options.age.range_45_54.short - t: 45-54 + t: 46-54 - key: options.age.range_55_64.short - t: 55-64 + t: 56-64 - key: options.age.range_more_than_65.short t: '>65' @@ -480,13 +480,13 @@ translations: t: 1 to 2 years - key: options.years_of_experience.range_2_5 - t: 2 to 5 years + t: 3 to 5 years - key: options.years_of_experience.range_5_10 - t: 5 to 10 years + t: 6 to 10 years - key: options.years_of_experience.range_10_20 - t: 10 to 20 years + t: 11 to 20 years - key: options.years_of_experience.range_more_than_20 t: More than 20 years @@ -499,13 +499,13 @@ translations: t: 1-2 years - key: options.years_of_experience.range_2_5.short - t: 2-5 years + t: 3-5 years - key: options.years_of_experience.range_5_10.short - t: 5-10 years + t: 6-10 years - key: options.years_of_experience.range_10_20.short - t: 10-20 years + t: 11-20 years - key: options.years_of_experience.range_more_than_20.short t: '>20 years' @@ -515,22 +515,22 @@ translations: t: One employee - key: options.company_size.range_1_5 - t: 1 to 5 employees + t: 2 to 5 employees - key: options.company_size.range_5_10 - t: 5 to 10 employees + t: 6 to 10 employees - key: options.company_size.range_10_20 - t: 10 to 20 employees + t: 11 to 20 employees - key: options.company_size.range_20_50 - t: 20 to 50 employees + t: 21 to 50 employees - key: options.company_size.range_50_100 - t: 50 to 100 employees + t: 51 to 100 employees - key: options.company_size.range_100_1000 - t: 100 to 1000 employees + t: 101 to 1000 employees - key: options.company_size.range_more_than_1000 t: More than 1000 employees @@ -543,19 +543,19 @@ translations: t: 1-5 - key: options.company_size.range_5_10.short - t: 5-10 + t: 6-10 - key: options.company_size.range_10_20.short - t: 10-20 + t: 11-20 - key: options.company_size.range_20_50.short - t: 20-50 + t: 21-50 - key: options.company_size.range_50_100.short - t: 50-100 + t: 51-100 - key: options.company_size.range_100_1000.short - t: 100-1000 + t: 101-1000 - key: options.company_size.range_more_than_1000.short t: '>1000' From 53097c3eb2daada46ee07a939646916089638cc1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:41:12 +0900 Subject: [PATCH 0727/1932] New translations surveys.yml (Swedish) --- sv/surveys.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/sv/surveys.yml b/sv/surveys.yml index 99cb51b8c6f..4f3e1e327d0 100644 --- a/sv/surveys.yml +++ b/sv/surveys.yml @@ -10,6 +10,33 @@ translations: - key: general.global_nav t: Global + - + ########################################################################### + #Accounts + ########################################################################### + key: accounts.create_account + t: Create an Account + - + key: accounts.create_account.description + t: Having an account lets you **access your own data in the future** and be notified when survey results are published. + - + key: accounts.create_account.note + t: If you **already have an account** we will send you a magic log-in link by email. + - + key: accounts.create_account.action + t: Continue with Account + - + key: accounts.your_email + t: Your Email + - + key: accounts.continue_as_guest + t: Continue as Guest + - + key: accounts.continue_as_guest.description + t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + - + key: accounts.continue_as_guest.action + t: Continue as Guest - ########################################################################### #FAQ From fe0bd35dd801bdc869c58379d6bc21bc85e2ea98 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 21 May 2022 07:41:13 +0900 Subject: [PATCH 0728/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index 00c053449f1..2ed9b0918d5 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -16,6 +16,10 @@ translations: key: tools.tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! + - + key: usage.bracket_intro + t: > + The next question uses a special **bracket** format! For each match-up, pick the item that you feel is most important to you (note that match-ups are randomized for every respondent). - ########################################################################### #Sections @@ -176,6 +180,15 @@ translations: - key: features.schema_stitching t: Schema Stitching + - + ########################################################################### + #Tools + ########################################################################### + key: tools.no_client + t: No Client + - + key: tools.no_client.description + t: No dedicated GraphQL client (raw HTTP requests with Fetch, Axios, etc.) - ########################################################################### #Other Tools From cfa55a49eb9fc745f3a5812b3b3ae2ea04c22844 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:38 +0900 Subject: [PATCH 0729/1932] New translations common.yml (Romanian) --- ro/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/ro/common.yml b/ro/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 8ad1e5b37942bf1494b54e1c1aea9af5cce3a701 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:39 +0900 Subject: [PATCH 0730/1932] New translations surveys.yml (Hungarian) --- hu/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/hu/surveys.yml b/hu/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/hu/surveys.yml +++ b/hu/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 8d135869346b854f111a3606988a5ffe2222108d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:40 +0900 Subject: [PATCH 0731/1932] New translations surveys.yml (Greek) --- el/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/el/surveys.yml b/el/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/el/surveys.yml +++ b/el/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 17abbb12dc7cb69e0ae6f90d66e46841d30bb239 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:41 +0900 Subject: [PATCH 0732/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 7b66292614e54f39a84ca1e342e4395fe068ad30 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:42 +0900 Subject: [PATCH 0733/1932] New translations common.yml (Finnish) --- fi/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/fi/common.yml b/fi/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 75d7733afb468dc7e599ba8005ac7767582f3105 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:43 +0900 Subject: [PATCH 0734/1932] New translations surveys.yml (Finnish) --- fi/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/fi/surveys.yml b/fi/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/fi/surveys.yml +++ b/fi/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 4de6d3e87b746ecb0bc8c0ce75d22df981597984 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:44 +0900 Subject: [PATCH 0735/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 2dbee4287828ff38fbe20147e851890e19aef497 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:45 +0900 Subject: [PATCH 0736/1932] New translations common.yml (Hebrew) --- he/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/he/common.yml b/he/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/he/common.yml +++ b/he/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From c7ab9b5a36587cfb43911bf82d9b7a3f93157ae8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:46 +0900 Subject: [PATCH 0737/1932] New translations surveys.yml (Hebrew) --- he/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/he/surveys.yml b/he/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/he/surveys.yml +++ b/he/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From d4d3aed1f1435366a18002fde1934a78f658a0d6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:47 +0900 Subject: [PATCH 0738/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 030074d09a2e280bbfc01078d2037e46cea548e4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:48 +0900 Subject: [PATCH 0739/1932] New translations common.yml (Hungarian) --- hu/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/hu/common.yml b/hu/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 406102798bfd8332e08b24e9a10a50e58d9cca02 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:49 +0900 Subject: [PATCH 0740/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From cc8c2ff78c5defa5a70fc1da6321c7b529709aa7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:50 +0900 Subject: [PATCH 0741/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 905ca5e436b023313df8830fa2fafea513a7a6e6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:51 +0900 Subject: [PATCH 0742/1932] New translations common.yml (Italian) --- it/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/it/common.yml b/it/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/it/common.yml +++ b/it/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 57c71e4042f30f1898ae46b467e523d3736a3856 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:51 +0900 Subject: [PATCH 0743/1932] New translations surveys.yml (Italian) --- it/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/it/surveys.yml b/it/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/it/surveys.yml +++ b/it/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 5487e7bb36f3fa9e8bcd751468de63b4d9117327 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:52 +0900 Subject: [PATCH 0744/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From afbad8a5dee3b65b0557c78c131ea3abf90649c7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:54 +0900 Subject: [PATCH 0745/1932] New translations common.yml (Japanese) --- ja/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/ja/common.yml b/ja/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 23b939d47afc9204638add8bec191b38aa18232b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:54 +0900 Subject: [PATCH 0746/1932] New translations surveys.yml (Japanese) --- ja/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/ja/surveys.yml b/ja/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/ja/surveys.yml +++ b/ja/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From e9e7638277aee52b4744a59bab932445ad768f53 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:55 +0900 Subject: [PATCH 0747/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 59ca1151a65d45b9a114ea775b70da8593d997f6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:56 +0900 Subject: [PATCH 0748/1932] New translations common.yml (Korean) --- ko/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/ko/common.yml b/ko/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 1bd1da5909a54064ee05e0d33151eb822985ba9f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:57 +0900 Subject: [PATCH 0749/1932] New translations surveys.yml (Korean) --- ko/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/ko/surveys.yml b/ko/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/ko/surveys.yml +++ b/ko/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 90b0b31cff4365b9c399fd9786bb3f5151518eb8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:58 +0900 Subject: [PATCH 0750/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From f311adf86b24557fe4f75382a86f19f621ceafa5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:56:59 +0900 Subject: [PATCH 0751/1932] New translations common.yml (Dutch) --- nl/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/nl/common.yml b/nl/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From f8ffba08d9774124524738c6074656e2b1373909 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:02 +0900 Subject: [PATCH 0752/1932] New translations common.yml (Greek) --- el/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/el/common.yml b/el/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/el/common.yml +++ b/el/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 770e5ce98c2f54c2ee18bdf997ccccac5b4cb12c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:03 +0900 Subject: [PATCH 0753/1932] New translations surveys.yml (German) --- de/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/de/surveys.yml b/de/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/de/surveys.yml +++ b/de/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From c1ee5103044e6dda91f9e74b865c03f6fe012798 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:04 +0900 Subject: [PATCH 0754/1932] New translations surveys.yml (Romanian) --- ro/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/ro/surveys.yml b/ro/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/ro/surveys.yml +++ b/ro/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 96b9fd37cb24190de5a6ca3ad0036200291c42d6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:05 +0900 Subject: [PATCH 0755/1932] New translations common.yml (Arabic) --- ar/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/ar/common.yml b/ar/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 9a09233865450893cda860dc606558da6449c210 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:06 +0900 Subject: [PATCH 0756/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 82c962538e886138c4f70cd11036a3f25b583791 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:07 +0900 Subject: [PATCH 0757/1932] New translations common.yml (French) --- fr/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/fr/common.yml b/fr/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From e337ffadc74573560d728930579411be1f0666b2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:08 +0900 Subject: [PATCH 0758/1932] New translations surveys.yml (French) --- fr/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/fr/surveys.yml b/fr/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/fr/surveys.yml +++ b/fr/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From ec0afabeebd7edb0bee2a1579584059ea9040d13 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:09 +0900 Subject: [PATCH 0759/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From d07b69563d0b33224d7a05a8b09f57407480cc3e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:10 +0900 Subject: [PATCH 0760/1932] New translations common.yml (Spanish) --- es/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/es/common.yml b/es/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/es/common.yml +++ b/es/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 774e55f84c6db35c51eedc89867ce236063eacad Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:11 +0900 Subject: [PATCH 0761/1932] New translations surveys.yml (Spanish) --- es/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/es/surveys.yml b/es/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/es/surveys.yml +++ b/es/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 7cab5a7d5c5563b6ed1c84d97098f686cc6782aa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:12 +0900 Subject: [PATCH 0762/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 6fc324fee9a50b84f53e2c5f98147b445aa048a6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:13 +0900 Subject: [PATCH 0763/1932] New translations common.yml (Afrikaans) --- af/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/af/common.yml b/af/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/af/common.yml +++ b/af/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From b6e84f9b542a2b70608865927538f891f81f1167 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:14 +0900 Subject: [PATCH 0764/1932] New translations surveys.yml (Afrikaans) --- af/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/af/surveys.yml b/af/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/af/surveys.yml +++ b/af/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 9fc4c5635e51a7e32584ce382dd6144a4067918f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:15 +0900 Subject: [PATCH 0765/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 5b3c7c3fd7a4e0f2e4119de4d53fe03f55bdf1a5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:16 +0900 Subject: [PATCH 0766/1932] New translations surveys.yml (Arabic) --- ar/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/ar/surveys.yml b/ar/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/ar/surveys.yml +++ b/ar/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From af6ba4afd6b9bd5fd8ce6c0c0e2f521dd7435285 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:17 +0900 Subject: [PATCH 0767/1932] New translations common.yml (German) --- de/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/de/common.yml b/de/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/de/common.yml +++ b/de/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 70485dca1d89b3331ee85e371dc3bcebb782a5bc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:18 +0900 Subject: [PATCH 0768/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From cb105a8e007ce5b3cf344784e2636b6e8d3ac810 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:19 +0900 Subject: [PATCH 0769/1932] New translations common.yml (Catalan) --- ca/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/ca/common.yml b/ca/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From ededf04f88bb8881bf40808afcb13e3f0074477f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:20 +0900 Subject: [PATCH 0770/1932] New translations surveys.yml (Catalan) --- ca/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/ca/surveys.yml b/ca/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/ca/surveys.yml +++ b/ca/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From a1f92f9a6ccf93e5460cb9af41f6b46f4dd33f34 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:21 +0900 Subject: [PATCH 0771/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 8b827b1aa47d0866544ba44a53760dc4a9a5bd7f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:22 +0900 Subject: [PATCH 0772/1932] New translations common.yml (Czech) --- cs/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/cs/common.yml b/cs/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From e6bbb74eb46703cfd1977c7f0ba1e560fad93487 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:23 +0900 Subject: [PATCH 0773/1932] New translations surveys.yml (Czech) --- cs/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/cs/surveys.yml b/cs/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/cs/surveys.yml +++ b/cs/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 4f633c7d982f99631ec7f779b5250e83911ed822 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:24 +0900 Subject: [PATCH 0774/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From b0067e422d22947278178d0af8e8b112d9e2890a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:25 +0900 Subject: [PATCH 0775/1932] New translations common.yml (Danish) --- da/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/da/common.yml b/da/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/da/common.yml +++ b/da/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From bac3d9d2c161d3742e4c18d3ac472f7c6153c576 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:26 +0900 Subject: [PATCH 0776/1932] New translations surveys.yml (Danish) --- da/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/da/surveys.yml b/da/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/da/surveys.yml +++ b/da/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From fbea6296f01e1ed126c2b0751347535d65b9a682 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:27 +0900 Subject: [PATCH 0777/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 9dc69c52c077c53b903f1c88de1b5888a17a6172 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:28 +0900 Subject: [PATCH 0778/1932] New translations surveys.yml (Dutch) --- nl/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/nl/surveys.yml b/nl/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/nl/surveys.yml +++ b/nl/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From cbc44adf9f445ae47e53f1f1bc6679807bc4b384 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:29 +0900 Subject: [PATCH 0779/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 7069d15e015d94279ea9a93311930bd19c4d119c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:30 +0900 Subject: [PATCH 0780/1932] New translations common.yml (Norwegian) --- no/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/no/common.yml b/no/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/no/common.yml +++ b/no/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From ba0411935befb354a549c8fc9f9970fff77d8cdf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:31 +0900 Subject: [PATCH 0781/1932] New translations accounts.yml (German) --- de/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/de/accounts.yml b/de/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/de/accounts.yml +++ b/de/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From d4635365f3bf4573a6905711914efd3f7e7864bd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:32 +0900 Subject: [PATCH 0782/1932] New translations accounts.yml (Danish) --- da/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/da/accounts.yml b/da/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/da/accounts.yml +++ b/da/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 4250ef29a8d6853ca391d5c2b540b1b2603e49e5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:33 +0900 Subject: [PATCH 0783/1932] New translations accounts.yml (Czech) --- cs/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/cs/accounts.yml b/cs/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/cs/accounts.yml +++ b/cs/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 37837112b05f764fe2c3c631e3271a19057c4c91 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:34 +0900 Subject: [PATCH 0784/1932] New translations accounts.yml (Catalan) --- ca/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ca/accounts.yml b/ca/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/ca/accounts.yml +++ b/ca/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From e7295276c2fe02828d7aad56c358a01bcb5d0343 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:35 +0900 Subject: [PATCH 0785/1932] New translations accounts.yml (Arabic) --- ar/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ar/accounts.yml b/ar/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/ar/accounts.yml +++ b/ar/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From c7e357a15a42e1aa0ced9d609ffbb48d1789b5f1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:36 +0900 Subject: [PATCH 0786/1932] New translations accounts.yml (Afrikaans) --- af/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/af/accounts.yml b/af/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/af/accounts.yml +++ b/af/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 67a53bf11cf52fe4a1f82d0744bdc3f3131d631d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:37 +0900 Subject: [PATCH 0787/1932] New translations accounts.yml (Spanish) --- es/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/es/accounts.yml b/es/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/es/accounts.yml +++ b/es/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From a7f7cb8be9e3d0efa1b9c2ffe5e5f9270471987b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:38 +0900 Subject: [PATCH 0788/1932] New translations accounts.yml (French) --- fr/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/fr/accounts.yml b/fr/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/fr/accounts.yml +++ b/fr/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From f5df5e6e3d8fc8045e0468dee2d909ed3658b72d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:39 +0900 Subject: [PATCH 0789/1932] New translations accounts.yml (Romanian) --- ro/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ro/accounts.yml b/ro/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/ro/accounts.yml +++ b/ro/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From fc21121606a8b5b37eed6f1cc8d96756d631fcda Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:40 +0900 Subject: [PATCH 0790/1932] New translations accounts.yml (Greek) --- el/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/el/accounts.yml b/el/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/el/accounts.yml +++ b/el/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From ae48ef9a680a106337c2af07949f080d22960bfe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:40 +0900 Subject: [PATCH 0791/1932] New translations surveys.yml (Norwegian) --- no/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/no/surveys.yml b/no/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/no/surveys.yml +++ b/no/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 25c514b9aa4bfa41345ddecaf503e1d315fdd26e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:41 +0900 Subject: [PATCH 0792/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From bc61c8ae4ccb3d079c16654a05f8e218fde730bc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:42 +0900 Subject: [PATCH 0793/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 7c22ea2dd5f662fd4859fcdf02521e3bc0e0177c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:43 +0900 Subject: [PATCH 0794/1932] New translations state_of_graphql.yml (Portuguese, Brazilian) --- pt/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 72c8419e4538ad247fd9842453408c3fab8f850c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:44 +0900 Subject: [PATCH 0795/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/vi/common.yml b/vi/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From adb5ff7b58dcd54225ae38c9b6beefcd4a30414f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:45 +0900 Subject: [PATCH 0796/1932] New translations surveys.yml (Vietnamese) --- vi/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/vi/surveys.yml b/vi/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/vi/surveys.yml +++ b/vi/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 2f92c7c9032cfbbc4165514fe8c7da5d13bb1bc1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:46 +0900 Subject: [PATCH 0797/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From c51f693ab2da1efb4f9f2f89ea7566f1bf1a4220 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:47 +0900 Subject: [PATCH 0798/1932] New translations common.yml (Portuguese, Brazilian) --- pt/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/pt/common.yml b/pt/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 8e5f2cf7a022bf1d6542598467518b7fb43c88be Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:49 +0900 Subject: [PATCH 0799/1932] New translations surveys.yml (Portuguese, Brazilian) --- pt/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/pt/surveys.yml b/pt/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/pt/surveys.yml +++ b/pt/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 8be2fa17642d66230438e407304daeb67e739827 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:51 +0900 Subject: [PATCH 0800/1932] New translations common.yml (Russian) --- ru/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/ru/common.yml b/ru/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From a3dbd8ae98571836c98d35a56c2c078b2bdf583c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:52 +0900 Subject: [PATCH 0801/1932] New translations surveys.yml (English) --- en/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/en/surveys.yml b/en/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/en/surveys.yml +++ b/en/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From df97da65253e2cdfc4e0762f2f7eaf7e5d5f403d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:55 +0900 Subject: [PATCH 0802/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 68df68332473c6578974615cdba12cec84c3315f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:55 +0900 Subject: [PATCH 0803/1932] New translations surveys.yml (Polish) --- pl/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/pl/surveys.yml b/pl/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/pl/surveys.yml +++ b/pl/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 777a6df252b8f366a29476f0b2ccb52e0f90d161 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:56 +0900 Subject: [PATCH 0804/1932] New translations common.yml (Polish) --- pl/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/pl/common.yml b/pl/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From f6291d79762f0e4cc426f12d1c134269d66778b3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:58 +0900 Subject: [PATCH 0805/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From a78aa4728e48296c3c6f29ce7d8fa11eadb0d611 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:57:59 +0900 Subject: [PATCH 0806/1932] New translations common.yml (English) --- en/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/en/common.yml b/en/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/en/common.yml +++ b/en/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 2c4ce5dd906ce0c6f781858e6a6cef30578164ca Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:00 +0900 Subject: [PATCH 0807/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/sr/common.yml b/sr/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 25c70826ff3fa5ecbb9d8b7d8f847f77df427eb6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:01 +0900 Subject: [PATCH 0808/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 51fb7286e9544c0e7605f8a24f09b872fce9410c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:02 +0900 Subject: [PATCH 0809/1932] New translations surveys.yml (Serbian (Cyrillic)) --- sr/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/sr/surveys.yml b/sr/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/sr/surveys.yml +++ b/sr/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 23bcb29939ceb4575298ab261fe9af77af0f930f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:03 +0900 Subject: [PATCH 0810/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From de35d0027b01c1651f0611e87ff0b8d3dfe19c68 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:04 +0900 Subject: [PATCH 0811/1932] New translations common.yml (Swedish) --- sv/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/sv/common.yml b/sv/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From af05639adf579066b157ec443b51e8ee03dc86b4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:05 +0900 Subject: [PATCH 0812/1932] New translations surveys.yml (Swedish) --- sv/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/sv/surveys.yml b/sv/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/sv/surveys.yml +++ b/sv/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From a9a80ab1beca5f7f8b21f99b3c59cbab1f5af82b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:06 +0900 Subject: [PATCH 0813/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From b2b2c4cd84950dfb2e6fa7990baf9f5583c3f476 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:07 +0900 Subject: [PATCH 0814/1932] New translations common.yml (Turkish) --- tr/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/tr/common.yml b/tr/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From d7a17d8210acdcec24623fb67f075149bf71f5ca Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:08 +0900 Subject: [PATCH 0815/1932] New translations surveys.yml (Turkish) --- tr/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/tr/surveys.yml b/tr/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/tr/surveys.yml +++ b/tr/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 20f6a4f74cced3ee9a9f6a99766ebc2808c89b1b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:09 +0900 Subject: [PATCH 0816/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/uk/common.yml b/uk/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From bf46af837389582051771714b6aa9792406c9ec3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:10 +0900 Subject: [PATCH 0817/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From e88a01bcd0250c8aa12e04c204626addf34b0041 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:11 +0900 Subject: [PATCH 0818/1932] New translations surveys.yml (Ukrainian) --- uk/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/uk/surveys.yml b/uk/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/uk/surveys.yml +++ b/uk/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From b31aa343b978ea40796ba8debbc1fee70734f107 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:12 +0900 Subject: [PATCH 0819/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index 2ed9b0918d5..a305db3301d 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -6,6 +6,14 @@ translations: ########################################################################### #General ########################################################################### + key: general.survey_intro_graphql2022 + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - ########################################################################### #Survey ########################################################################### @@ -355,6 +363,27 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which GraphQL-related sites/courses/etc. do you use to learn about GraphQL? + - + #podcasts + key: resources.podcasts.others + t: Podcasts + - + key: resources.podcasts.others.description + t: Which GraphQL-related podcasts do you listen to? + - + #people + key: resources.people.others + t: People + - + key: resources.people.others.description + t: People you read, follow, or just want to highlight for their work in the GraphQL ecosystem. - ########################################################################### #Options From 6fe7ea7d8826c518b87c3d873131f413f4754e43 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:13 +0900 Subject: [PATCH 0820/1932] New translations surveys.yml (Russian) --- ru/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/ru/surveys.yml b/ru/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/ru/surveys.yml +++ b/ru/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 0474a587d116093136d8628e6e3afdaef000bf9d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:14 +0900 Subject: [PATCH 0821/1932] New translations surveys.yml (Chinese Simplified) --- zh/surveys.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/zh/surveys.yml b/zh/surveys.yml index 4f3e1e327d0..1b3e2965515 100644 --- a/zh/surveys.yml +++ b/zh/surveys.yml @@ -33,10 +33,16 @@ translations: t: Continue as Guest - key: accounts.continue_as_guest.description - t: Taking the survey anonymously means you **won't be able to access your data again** after you close your browser tab. + t: Taking the survey anonymously means you **won't be able to access your data again** after you end your session. - key: accounts.continue_as_guest.action t: Continue as Guest + - + key: accounts.magic_link.no_email + t: Please enter your email + - + key: accounts.magic_link.success + t: Check your inbox! We sent you a magic link, just click it to confirm your account and log in. - ########################################################################### #FAQ From 3a9864fac0353f42e6059e4437f78729ae9a6f55 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:16 +0900 Subject: [PATCH 0822/1932] New translations common.yml (Chinese Traditional) --- zh/common.yml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/zh/common.yml b/zh/common.yml index 6cb7380b7d8..674207e8ef2 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -103,6 +103,12 @@ translations: #credits key: credits.thanks t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. - key: credits.accessibility t: Accessibility Consulting @@ -171,8 +177,8 @@ translations: - key: general.thanks t: > - Thanks for filling out the survey! - Your data is saved. You can review or modify it until the survey closes. + Thanks for filling out the survey! Your data is saved. + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: - key: thanks.learn_more_about @@ -1215,6 +1221,10 @@ translations: - key: user_info.email t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. - key: user_info.country t: Your Country or Region From 6cfa217e2ce6ed8af3e46310b1ecbe6704197d58 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:19 +0900 Subject: [PATCH 0823/1932] New translations accounts.yml (Finnish) --- fi/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/fi/accounts.yml b/fi/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/fi/accounts.yml +++ b/fi/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From f1a9e338c167adef2fb375132bb941c4ea87a6cd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:20 +0900 Subject: [PATCH 0824/1932] New translations accounts.yml (Hungarian) --- hu/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/hu/accounts.yml b/hu/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/hu/accounts.yml +++ b/hu/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From a02e01a93a3b8ebedd9cbd8bf9c58722ba04f737 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:20 +0900 Subject: [PATCH 0825/1932] New translations accounts.yml (Italian) --- it/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/it/accounts.yml b/it/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/it/accounts.yml +++ b/it/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 947668d2bfdb22bc2d31457be26fe1515ea472d8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:21 +0900 Subject: [PATCH 0826/1932] New translations accounts.yml (Japanese) --- ja/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ja/accounts.yml b/ja/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/ja/accounts.yml +++ b/ja/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 128c7c443b5b50768102ecbca33576bc1ee118cb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:22 +0900 Subject: [PATCH 0827/1932] New translations accounts.yml (Korean) --- ko/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ko/accounts.yml b/ko/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/ko/accounts.yml +++ b/ko/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 2ca55f498bce9bf6c98b223d8698c5a485a1d3a6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:23 +0900 Subject: [PATCH 0828/1932] New translations accounts.yml (Dutch) --- nl/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/nl/accounts.yml b/nl/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/nl/accounts.yml +++ b/nl/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From f8a4af6224825e3941b58cb6b58bb58562ccfea4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:24 +0900 Subject: [PATCH 0829/1932] New translations accounts.yml (Norwegian) --- no/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/no/accounts.yml b/no/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/no/accounts.yml +++ b/no/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 8922684260c0da6f03785ca95a617e889e40e0dd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:25 +0900 Subject: [PATCH 0830/1932] New translations accounts.yml (Hebrew) --- he/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/he/accounts.yml b/he/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/he/accounts.yml +++ b/he/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From b1de0a98a13c781c14be2dcdb277887911ddada2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:26 +0900 Subject: [PATCH 0831/1932] New translations accounts.yml (Ukrainian) --- uk/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/uk/accounts.yml b/uk/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/uk/accounts.yml +++ b/uk/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 89d0b865941c46f4ba43260280a4a19299980c73 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:27 +0900 Subject: [PATCH 0832/1932] New translations accounts.yml (Vietnamese) --- vi/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/vi/accounts.yml b/vi/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/vi/accounts.yml +++ b/vi/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From e2eca5ef24d5dd3889440a234cee27741a8019da Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:28 +0900 Subject: [PATCH 0833/1932] New translations accounts.yml (English) --- en/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/en/accounts.yml b/en/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/en/accounts.yml +++ b/en/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From f4c6959a389cf2579cb23293782d1405f5c45d7a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:29 +0900 Subject: [PATCH 0834/1932] New translations accounts.yml (Chinese Traditional) --- zh/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/zh/accounts.yml b/zh/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/zh/accounts.yml +++ b/zh/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 7c254c52e115f4ab60261e47b758786cce289e3b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:30 +0900 Subject: [PATCH 0835/1932] New translations accounts.yml (Russian) --- ru/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/ru/accounts.yml b/ru/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/ru/accounts.yml +++ b/ru/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From aa63d5a3a5d47fe8f5509ac9d17fc57610057773 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:31 +0900 Subject: [PATCH 0836/1932] New translations accounts.yml (Turkish) --- tr/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/tr/accounts.yml b/tr/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/tr/accounts.yml +++ b/tr/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From c8d7eb47610ec22abdc2f1ac59c0c5ab424df875 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:32 +0900 Subject: [PATCH 0837/1932] New translations accounts.yml (Swedish) --- sv/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/sv/accounts.yml b/sv/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/sv/accounts.yml +++ b/sv/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 6e2bfe83361fc0182c4014a1d336b00d0384260f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:33 +0900 Subject: [PATCH 0838/1932] New translations accounts.yml (Serbian (Cyrillic)) --- sr/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/sr/accounts.yml b/sr/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/sr/accounts.yml +++ b/sr/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 3838b35ec691156829b8f2042dd6e3aa7ce206aa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:34 +0900 Subject: [PATCH 0839/1932] New translations accounts.yml (Portuguese) --- pt/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/pt/accounts.yml b/pt/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/pt/accounts.yml +++ b/pt/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 8adb82df653f3411d7eb763729da4b5be3fff27c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 25 May 2022 11:58:35 +0900 Subject: [PATCH 0840/1932] New translations accounts.yml (Polish) --- pl/accounts.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/pl/accounts.yml b/pl/accounts.yml index 03c4279ca1f..141b52d0949 100644 --- a/pl/accounts.yml +++ b/pl/accounts.yml @@ -109,7 +109,13 @@ translations: - key: accounts.logged_in_as t: Logged in as {email} + - + key: accounts.logged_in_as_guest + t: Logged in as Guest - key: accounts.questions t: > If you have any questions about how we use your data, or would like us to remove your data from our records, please get in touch. + - + key: accounts.token_verified + t: Token verification successful, redirecting… From 8541d6e86a6959c64971905f7ce735a0eeccec40 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:47 +0900 Subject: [PATCH 0841/1932] New translations common.yml (Romanian) --- ro/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/ro/common.yml b/ro/common.yml index 674207e8ef2..512b402adca 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 4158ae202ede8e489e2f7941e7295226c5a36d3d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:48 +0900 Subject: [PATCH 0842/1932] New translations surveys.yml (Polish) --- pl/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pl/surveys.yml b/pl/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/pl/surveys.yml +++ b/pl/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 3795f566b54c6794266faad8a08941f9ab8363c4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:49 +0900 Subject: [PATCH 0843/1932] New translations common.yml (Japanese) --- ja/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/ja/common.yml b/ja/common.yml index 674207e8ef2..512b402adca 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From c5d9b34a6ea742c099e023611160cb11e349f500 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:50 +0900 Subject: [PATCH 0844/1932] New translations surveys.yml (Japanese) --- ja/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/surveys.yml b/ja/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/ja/surveys.yml +++ b/ja/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 6be113b1e70d881ad4e2a01a789f097c668d7ed6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:51 +0900 Subject: [PATCH 0845/1932] New translations common.yml (Korean) --- ko/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/ko/common.yml b/ko/common.yml index 674207e8ef2..512b402adca 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From d3833fe2e1f40eb657ecc9d6bbea64cc0c0db75a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:52 +0900 Subject: [PATCH 0846/1932] New translations surveys.yml (Korean) --- ko/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/surveys.yml b/ko/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/ko/surveys.yml +++ b/ko/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From e204418091d4e2ac3d5647f543626d95c1dd02ee Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:53 +0900 Subject: [PATCH 0847/1932] New translations common.yml (Dutch) --- nl/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/nl/common.yml b/nl/common.yml index 674207e8ef2..512b402adca 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From e0f05b1aff475f7f80c6a3e33733e93274a6515e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:54 +0900 Subject: [PATCH 0848/1932] New translations surveys.yml (Dutch) --- nl/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nl/surveys.yml b/nl/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/nl/surveys.yml +++ b/nl/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 714dda0b30781888f088de0445e59dd3fafe3dd9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:55 +0900 Subject: [PATCH 0849/1932] New translations common.yml (Norwegian) --- no/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/no/common.yml b/no/common.yml index 674207e8ef2..512b402adca 100644 --- a/no/common.yml +++ b/no/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 0d0de57c5b9a631537ca0ccfb7c8d3ea9a6624b9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:56 +0900 Subject: [PATCH 0850/1932] New translations surveys.yml (Norwegian) --- no/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/no/surveys.yml b/no/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/no/surveys.yml +++ b/no/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 409dee56381665144a51a1a163191e4e5a8d82aa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:57 +0900 Subject: [PATCH 0851/1932] New translations common.yml (Polish) --- pl/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/pl/common.yml b/pl/common.yml index 674207e8ef2..512b402adca 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From c52112efd28a49525a19a2d50977cc55e88f0d36 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:58 +0900 Subject: [PATCH 0852/1932] New translations common.yml (Portuguese) --- pt/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/pt/common.yml b/pt/common.yml index 674207e8ef2..512b402adca 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From c48fb44c0677222a7e8f2c4f175f6d716220e6af Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:32:59 +0900 Subject: [PATCH 0853/1932] New translations common.yml (Italian) --- it/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/it/common.yml b/it/common.yml index 674207e8ef2..512b402adca 100644 --- a/it/common.yml +++ b/it/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From cfc6fe4d1a245476c223a5413ab0c4b43ecb084f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:01 +0900 Subject: [PATCH 0854/1932] New translations surveys.yml (Portuguese) --- pt/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pt/surveys.yml b/pt/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/pt/surveys.yml +++ b/pt/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 8dceb2808b2e52e0d1643ea5d1dbb0bf7620e1a1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:02 +0900 Subject: [PATCH 0855/1932] New translations common.yml (Russian) --- ru/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/ru/common.yml b/ru/common.yml index 674207e8ef2..512b402adca 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From bd45b917d241dbb6af86460d54d7240f04a6fdc0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:03 +0900 Subject: [PATCH 0856/1932] New translations surveys.yml (Russian) --- ru/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru/surveys.yml b/ru/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/ru/surveys.yml +++ b/ru/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 6140f303ef357008570a6affe47b5bd439565619 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:04 +0900 Subject: [PATCH 0857/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/sr/common.yml b/sr/common.yml index 674207e8ef2..512b402adca 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 158fc29263f1ab28f9dcf35d093db39ed26cbcd2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:05 +0900 Subject: [PATCH 0858/1932] New translations surveys.yml (Serbian (Cyrillic)) --- sr/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sr/surveys.yml b/sr/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/sr/surveys.yml +++ b/sr/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 6eb1a6dd83d46a27b664a406266331189813c344 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:06 +0900 Subject: [PATCH 0859/1932] New translations common.yml (Swedish) --- sv/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/sv/common.yml b/sv/common.yml index 674207e8ef2..512b402adca 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 9fd45c52d691938762a99a4c78817d617e799d20 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:07 +0900 Subject: [PATCH 0860/1932] New translations surveys.yml (Swedish) --- sv/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv/surveys.yml b/sv/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/sv/surveys.yml +++ b/sv/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 8fb11c3bae859feaa14ed650ae5852f6a11cb87c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:08 +0900 Subject: [PATCH 0861/1932] New translations common.yml (Turkish) --- tr/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/tr/common.yml b/tr/common.yml index 674207e8ef2..512b402adca 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 605a923b631e20ece3e326e5737a656d5ed259a6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:09 +0900 Subject: [PATCH 0862/1932] New translations surveys.yml (Turkish) --- tr/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/surveys.yml b/tr/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/tr/surveys.yml +++ b/tr/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From b162b2643aaf4cfcecf4f073f226d325d8042716 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:10 +0900 Subject: [PATCH 0863/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/uk/common.yml b/uk/common.yml index 674207e8ef2..512b402adca 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 2a1647a55c25861519578ff4b7fce17cf23a884c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:11 +0900 Subject: [PATCH 0864/1932] New translations surveys.yml (Italian) --- it/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/it/surveys.yml b/it/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/it/surveys.yml +++ b/it/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From aba7b7779940641d4c4e647a16f97125b50b2482 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:12 +0900 Subject: [PATCH 0865/1932] New translations surveys.yml (Hungarian) --- hu/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hu/surveys.yml b/hu/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/hu/surveys.yml +++ b/hu/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 28a09a545d1d7e3019ec92180f1144df78c34fba Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:13 +0900 Subject: [PATCH 0866/1932] New translations surveys.yml (Romanian) --- ro/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ro/surveys.yml b/ro/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/ro/surveys.yml +++ b/ro/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 9044883961f0f2a5e719f6b89e9cffc9f6a7a7f9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:14 +0900 Subject: [PATCH 0867/1932] New translations common.yml (Czech) --- cs/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/cs/common.yml b/cs/common.yml index 674207e8ef2..512b402adca 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From fc43806faf4524a75f8aed8f21f8be6aa6a36cc5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:15 +0900 Subject: [PATCH 0868/1932] New translations common.yml (French) --- fr/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/fr/common.yml b/fr/common.yml index 674207e8ef2..512b402adca 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 85a35e9f5aae43d0c09f2c960ee0e21222816df9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:16 +0900 Subject: [PATCH 0869/1932] New translations surveys.yml (French) --- fr/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/surveys.yml b/fr/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/fr/surveys.yml +++ b/fr/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 675c929a29a6db6bcc23998fe3ae434bf4ff4da4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:17 +0900 Subject: [PATCH 0870/1932] New translations common.yml (Spanish) --- es/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/es/common.yml b/es/common.yml index 674207e8ef2..512b402adca 100644 --- a/es/common.yml +++ b/es/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 2ecc7cfd7201b5b3842fd47b12bf877bd5f31cb4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:18 +0900 Subject: [PATCH 0871/1932] New translations surveys.yml (Spanish) --- es/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es/surveys.yml b/es/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/es/surveys.yml +++ b/es/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 4c72bcae2a3e7d1a0eb3aa2f47131543fbeea98e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:19 +0900 Subject: [PATCH 0872/1932] New translations common.yml (Afrikaans) --- af/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/af/common.yml b/af/common.yml index 674207e8ef2..512b402adca 100644 --- a/af/common.yml +++ b/af/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 70aca715190707674550809f800f57388bb8f84c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:20 +0900 Subject: [PATCH 0873/1932] New translations surveys.yml (Afrikaans) --- af/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/af/surveys.yml b/af/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/af/surveys.yml +++ b/af/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 7dcf0aab5a2eaa27261d112d3886c78e3b80d5bf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:21 +0900 Subject: [PATCH 0874/1932] New translations common.yml (Arabic) --- ar/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/ar/common.yml b/ar/common.yml index 674207e8ef2..512b402adca 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 04c80c6e3a64929d8ccc18b8ecbb13be658c85ae Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:22 +0900 Subject: [PATCH 0875/1932] New translations surveys.yml (Arabic) --- ar/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ar/surveys.yml b/ar/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/ar/surveys.yml +++ b/ar/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From d4dce3cf5b04337134a2c143a675ad42b8206016 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:23 +0900 Subject: [PATCH 0876/1932] New translations common.yml (Catalan) --- ca/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/ca/common.yml b/ca/common.yml index 674207e8ef2..512b402adca 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From c2c0c49f402d78c6b044cb5fdecaf1249868661e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:24 +0900 Subject: [PATCH 0877/1932] New translations surveys.yml (Catalan) --- ca/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ca/surveys.yml b/ca/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/ca/surveys.yml +++ b/ca/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From eb97cac2260ff8a6f579a535ea8b3b038e58341f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:25 +0900 Subject: [PATCH 0878/1932] New translations surveys.yml (Czech) --- cs/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/surveys.yml b/cs/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/cs/surveys.yml +++ b/cs/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 617abf676b29a2f582988120432a6ebd009a8360 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:26 +0900 Subject: [PATCH 0879/1932] New translations common.yml (Hungarian) --- hu/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/hu/common.yml b/hu/common.yml index 674207e8ef2..512b402adca 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From c94eaaa9ed51dcb65c22c63eed7fd547cf690d75 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:27 +0900 Subject: [PATCH 0880/1932] New translations common.yml (Danish) --- da/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/da/common.yml b/da/common.yml index 674207e8ef2..512b402adca 100644 --- a/da/common.yml +++ b/da/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 2448d057a4f7171dfe0da4274bcc2d2f8252ad94 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:28 +0900 Subject: [PATCH 0881/1932] New translations surveys.yml (Danish) --- da/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/da/surveys.yml b/da/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/da/surveys.yml +++ b/da/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 79c0d26dbbeceb40560054883a1c2e860c512ae9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:29 +0900 Subject: [PATCH 0882/1932] New translations common.yml (German) --- de/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/de/common.yml b/de/common.yml index 674207e8ef2..512b402adca 100644 --- a/de/common.yml +++ b/de/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 218082b09b575e54d034451e77d5ddf8cf45133e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:30 +0900 Subject: [PATCH 0883/1932] New translations surveys.yml (German) --- de/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/de/surveys.yml b/de/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/de/surveys.yml +++ b/de/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From c387f732896e1127704a38275fe4bf15fffba3d1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:31 +0900 Subject: [PATCH 0884/1932] New translations common.yml (Greek) --- el/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/el/common.yml b/el/common.yml index 674207e8ef2..512b402adca 100644 --- a/el/common.yml +++ b/el/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From ebccb4730ecdf6ca067416c3cb34ce95c238ce4e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:32 +0900 Subject: [PATCH 0885/1932] New translations surveys.yml (Greek) --- el/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/el/surveys.yml b/el/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/el/surveys.yml +++ b/el/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From e574816f6ede41931f5606ffabacfb7aa5055af3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:33 +0900 Subject: [PATCH 0886/1932] New translations common.yml (Finnish) --- fi/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/fi/common.yml b/fi/common.yml index 674207e8ef2..512b402adca 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 80637d0e2bdb7fb3b61b6a9f48a96be38024c7fe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:34 +0900 Subject: [PATCH 0887/1932] New translations surveys.yml (Finnish) --- fi/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi/surveys.yml b/fi/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/fi/surveys.yml +++ b/fi/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From eaa92491907d1c2957d2d00e48c03b2a5ff61ee8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:36 +0900 Subject: [PATCH 0888/1932] New translations common.yml (Hebrew) --- he/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/he/common.yml b/he/common.yml index 674207e8ef2..512b402adca 100644 --- a/he/common.yml +++ b/he/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 3076a3d9fd6074f0d319729b8e7f88baf8199f78 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:36 +0900 Subject: [PATCH 0889/1932] New translations surveys.yml (Hebrew) --- he/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/he/surveys.yml b/he/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/he/surveys.yml +++ b/he/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 6cd28c5f7abf958d13663c7bb63bb3a61ae487f8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:37 +0900 Subject: [PATCH 0890/1932] New translations surveys.yml (Ukrainian) --- uk/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/surveys.yml b/uk/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/uk/surveys.yml +++ b/uk/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From bad3fb49bc6d77bb44b24db48277eccae72aeec1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:38 +0900 Subject: [PATCH 0891/1932] New translations common.yml (Chinese Simplified) --- zh/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/zh/common.yml b/zh/common.yml index 674207e8ef2..512b402adca 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 750eabb84b2ab4beb3e3f45b7beccb7bfba64409 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:39 +0900 Subject: [PATCH 0892/1932] New translations homepage.yml (Russian) --- ru/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru/homepage.yml b/ru/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/ru/homepage.yml +++ b/ru/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 1e9058af89edc2ae7f5e0915a9880f3b17c24b79 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:40 +0900 Subject: [PATCH 0893/1932] New translations homepage.yml (Italian) --- it/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/it/homepage.yml b/it/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/it/homepage.yml +++ b/it/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 9bd954ca5aed0b94fea0772bcee871294acb852d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:41 +0900 Subject: [PATCH 0894/1932] New translations homepage.yml (Japanese) --- ja/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/homepage.yml b/ja/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/ja/homepage.yml +++ b/ja/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 6be3958682097687d538e2c7d8b498f5f00cb366 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:42 +0900 Subject: [PATCH 0895/1932] New translations homepage.yml (Korean) --- ko/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/homepage.yml b/ko/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/ko/homepage.yml +++ b/ko/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 9949f5d03a9e4f00b74bfeb7b671dd3c59cab2bf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:43 +0900 Subject: [PATCH 0896/1932] New translations homepage.yml (Dutch) --- nl/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nl/homepage.yml b/nl/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/nl/homepage.yml +++ b/nl/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 2933f9e2eba2741c3f8aa0dcc0e175e896328fe4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:44 +0900 Subject: [PATCH 0897/1932] New translations homepage.yml (Norwegian) --- no/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/no/homepage.yml b/no/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/no/homepage.yml +++ b/no/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 5798640a662beae87b593a23118a65d5d64de7d8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:45 +0900 Subject: [PATCH 0898/1932] New translations homepage.yml (Polish) --- pl/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pl/homepage.yml b/pl/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/pl/homepage.yml +++ b/pl/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From aec573fc57334e48bafa75907765c58143215a2a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:45 +0900 Subject: [PATCH 0899/1932] New translations homepage.yml (Portuguese) --- pt/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pt/homepage.yml b/pt/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/pt/homepage.yml +++ b/pt/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 96caafa2a561ff100a43fb21f11a60829aac2192 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:46 +0900 Subject: [PATCH 0900/1932] New translations homepage.yml (Serbian (Cyrillic)) --- sr/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sr/homepage.yml b/sr/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/sr/homepage.yml +++ b/sr/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 721f0dd9ce69751507602cfda7569b573c390d97 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:47 +0900 Subject: [PATCH 0901/1932] New translations homepage.yml (Hebrew) --- he/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/he/homepage.yml b/he/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/he/homepage.yml +++ b/he/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From ea7eec604d7d4eadbbf405f888faae9a88d4e626 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:48 +0900 Subject: [PATCH 0902/1932] New translations homepage.yml (Swedish) --- sv/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv/homepage.yml b/sv/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/sv/homepage.yml +++ b/sv/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 4c55dda71472ce7de764d70d0f2dd7fa0076e320 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:49 +0900 Subject: [PATCH 0903/1932] New translations homepage.yml (Turkish) --- tr/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/homepage.yml b/tr/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/tr/homepage.yml +++ b/tr/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 2cf0e82a4589afb053356bcddbb698040e625360 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:50 +0900 Subject: [PATCH 0904/1932] New translations homepage.yml (Ukrainian) --- uk/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/homepage.yml b/uk/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/uk/homepage.yml +++ b/uk/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From d2184cd0c8d94815ce47166ecc0f944861b7d3a2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:51 +0900 Subject: [PATCH 0905/1932] New translations homepage.yml (Chinese Simplified) --- zh/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/homepage.yml b/zh/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/zh/homepage.yml +++ b/zh/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 99c0a5fe72e8f27530f7f8073e5444afa80cbf2e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:52 +0900 Subject: [PATCH 0906/1932] New translations homepage.yml (English) --- en/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/homepage.yml b/en/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/en/homepage.yml +++ b/en/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 8d4766d90b66e505f40faf1c14040bbd1e39a7f3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:53 +0900 Subject: [PATCH 0907/1932] New translations homepage.yml (Vietnamese) --- vi/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vi/homepage.yml b/vi/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/vi/homepage.yml +++ b/vi/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From f361bef0f619f2ef5bf28be5cf455f5c27192b7f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:54 +0900 Subject: [PATCH 0908/1932] New translations homepage.yml (Hungarian) --- hu/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hu/homepage.yml b/hu/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/hu/homepage.yml +++ b/hu/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From d65c6f49aee832cd556224203bcb6ff4fd9685e0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:55 +0900 Subject: [PATCH 0909/1932] New translations homepage.yml (Finnish) --- fi/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi/homepage.yml b/fi/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/fi/homepage.yml +++ b/fi/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 3ac00c6c4451d9e74d050dbe63f4da484b402c25 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:56 +0900 Subject: [PATCH 0910/1932] New translations surveys.yml (Chinese Simplified) --- zh/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/surveys.yml b/zh/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/zh/surveys.yml +++ b/zh/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 6ef185066bbd81db72bbd691a7d4d3a223862662 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:33:59 +0900 Subject: [PATCH 0911/1932] New translations common.yml (English) --- en/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/en/common.yml b/en/common.yml index 674207e8ef2..512b402adca 100644 --- a/en/common.yml +++ b/en/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From 822cd2c022172d5d8abdcdccb7621e0749c2c042 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:00 +0900 Subject: [PATCH 0912/1932] New translations surveys.yml (English) --- en/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/surveys.yml b/en/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/en/surveys.yml +++ b/en/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From 6007458f85dfea37dc9f8d28a47a8201257b668a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:01 +0900 Subject: [PATCH 0913/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/vi/common.yml b/vi/common.yml index 674207e8ef2..512b402adca 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -1103,6 +1103,10 @@ translations: - key: options.bracket.combined t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published - ########################################################################### #Tools @@ -1202,6 +1206,10 @@ translations: key: user_info.race_ethnicity.note t: > While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. - #disability status key: user_info.disability_status @@ -1224,7 +1232,11 @@ translations: - key: user_info.email.description t: > - You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be notified when the survey results are published. + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. - key: user_info.country t: Your Country or Region @@ -1264,6 +1276,14 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - ########################################################################### #Other Tools From c6e50d7698c1169c684dbfd1aee1c22c1e258c38 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:02 +0900 Subject: [PATCH 0914/1932] New translations surveys.yml (Vietnamese) --- vi/surveys.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vi/surveys.yml b/vi/surveys.yml index 1b3e2965515..f437c01bf44 100644 --- a/vi/surveys.yml +++ b/vi/surveys.yml @@ -96,7 +96,7 @@ translations: t: Who runs these surveys? - key: faq.team.description - t: Surveys are primarily run by [me](http://sachagreif.com) in collaboration with contributors, translators, and volunteers. + t: Surveys are run by [Devographics](http://devographics.com) together with a collective of contributors, translators, and volunteers. - ########################################################################### #Form Controls From f6d9064bd624013b257508b1136b3e44267bf231 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:04 +0900 Subject: [PATCH 0915/1932] New translations homepage.yml (Romanian) --- ro/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ro/homepage.yml b/ro/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/ro/homepage.yml +++ b/ro/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From f8e7fcb308f2cc5766dee4b25dcf2818d726c3ee Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:05 +0900 Subject: [PATCH 0916/1932] New translations homepage.yml (Greek) --- el/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/el/homepage.yml b/el/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/el/homepage.yml +++ b/el/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 17de4a4962bcb2e5b2b2e0a0b365f5ce5907bcb6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:06 +0900 Subject: [PATCH 0917/1932] New translations homepage.yml (French) --- fr/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/homepage.yml b/fr/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/fr/homepage.yml +++ b/fr/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 861a64b397ec50e2391b66eb767e75845b2dc079 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:08 +0900 Subject: [PATCH 0918/1932] New translations homepage.yml (Spanish) --- es/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es/homepage.yml b/es/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/es/homepage.yml +++ b/es/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 10339f3ab80136aefab8c938cce15765b4af84d0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:09 +0900 Subject: [PATCH 0919/1932] New translations homepage.yml (Afrikaans) --- af/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/af/homepage.yml b/af/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/af/homepage.yml +++ b/af/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From ca3a6da9235a55188953cbe4ac02102843bf6c14 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:10 +0900 Subject: [PATCH 0920/1932] New translations homepage.yml (Arabic) --- ar/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ar/homepage.yml b/ar/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/ar/homepage.yml +++ b/ar/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 91e38583dc6f0e9953ccdf1936b6b03395393ee9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:10 +0900 Subject: [PATCH 0921/1932] New translations homepage.yml (Catalan) --- ca/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ca/homepage.yml b/ca/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/ca/homepage.yml +++ b/ca/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 5d2815605e234fcce7c20a2077ba9587a93990bb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:11 +0900 Subject: [PATCH 0922/1932] New translations homepage.yml (Czech) --- cs/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/homepage.yml b/cs/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/cs/homepage.yml +++ b/cs/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From e81e86c80e70e45f307675076fcc56040bfcb469 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:12 +0900 Subject: [PATCH 0923/1932] New translations homepage.yml (Danish) --- da/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/da/homepage.yml b/da/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/da/homepage.yml +++ b/da/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 4f0725e61fb42db70f691de2f38f4dfd3b72ca04 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 6 Jun 2022 14:34:13 +0900 Subject: [PATCH 0924/1932] New translations homepage.yml (German) --- de/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/de/homepage.yml b/de/homepage.yml index 51bcc5ae5be..6a83e7939b5 100644 --- a/de/homepage.yml +++ b/de/homepage.yml @@ -30,7 +30,7 @@ translations: t: Take Survey - key: homepage.view_results - t: View 2019 Results + t: View Results - key: share.help_spread t: Help Spread the Word! From 7ea320fd9462b88a2a2eee3ed57c7b7a9d47f524 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:30 +0900 Subject: [PATCH 0925/1932] New translations common.yml (Romanian) --- ro/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ro/common.yml b/ro/common.yml index 512b402adca..894c5fe6237 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From cb937c237953fa136d8b58628db1e3d5c2cd46f5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:31 +0900 Subject: [PATCH 0926/1932] New translations surveys.yml (Polish) --- pl/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/pl/surveys.yml b/pl/surveys.yml index f437c01bf44..8642847436a 100644 --- a/pl/surveys.yml +++ b/pl/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 497c87615b3c5b4f1872126889b1905371b23b6b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:33 +0900 Subject: [PATCH 0927/1932] New translations common.yml (Japanese) --- ja/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ja/common.yml b/ja/common.yml index 512b402adca..894c5fe6237 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From c737da9c3d292237916b1b7e60ed8ea768fbc1d0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:33 +0900 Subject: [PATCH 0928/1932] New translations surveys.yml (Japanese) --- ja/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/ja/surveys.yml b/ja/surveys.yml index f437c01bf44..8642847436a 100644 --- a/ja/surveys.yml +++ b/ja/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 76feed458c10568c587c6fed92e7d3dd4dc19048 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:34 +0900 Subject: [PATCH 0929/1932] New translations common.yml (Korean) --- ko/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ko/common.yml b/ko/common.yml index 512b402adca..894c5fe6237 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 82b719bdc50d4a6fe0030248733b5bdae87d1df7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:35 +0900 Subject: [PATCH 0930/1932] New translations surveys.yml (Korean) --- ko/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/ko/surveys.yml b/ko/surveys.yml index f437c01bf44..8642847436a 100644 --- a/ko/surveys.yml +++ b/ko/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From c51e456a948c30d4d22b1b9e5f32c2090d0d8598 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:36 +0900 Subject: [PATCH 0931/1932] New translations common.yml (Dutch) --- nl/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/nl/common.yml b/nl/common.yml index 512b402adca..894c5fe6237 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 89bf866eb9bb31a293513d8365f34e717856cb97 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:37 +0900 Subject: [PATCH 0932/1932] New translations surveys.yml (Dutch) --- nl/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/nl/surveys.yml b/nl/surveys.yml index f437c01bf44..8642847436a 100644 --- a/nl/surveys.yml +++ b/nl/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From cd8ec0fe710ebe0d20640c967e6e828b2cdbdfbe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:38 +0900 Subject: [PATCH 0933/1932] New translations common.yml (Norwegian) --- no/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/no/common.yml b/no/common.yml index 512b402adca..894c5fe6237 100644 --- a/no/common.yml +++ b/no/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From abea7b44d2005723cf99a0ce9ce255b8d6d3ba03 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:40 +0900 Subject: [PATCH 0934/1932] New translations surveys.yml (Norwegian) --- no/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/no/surveys.yml b/no/surveys.yml index f437c01bf44..8642847436a 100644 --- a/no/surveys.yml +++ b/no/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 71be99bac50d96a200c70172a6040604b510900a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:41 +0900 Subject: [PATCH 0935/1932] New translations common.yml (Polish) --- pl/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pl/common.yml b/pl/common.yml index 512b402adca..894c5fe6237 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 0a001900dbc49e841c911077c63a1e655e0c4065 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:42 +0900 Subject: [PATCH 0936/1932] New translations common.yml (Portuguese) --- pt/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pt/common.yml b/pt/common.yml index 512b402adca..894c5fe6237 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From f3b79048000b136121c44f779b43153daf26eca7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:43 +0900 Subject: [PATCH 0937/1932] New translations common.yml (Italian) --- it/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/it/common.yml b/it/common.yml index 512b402adca..894c5fe6237 100644 --- a/it/common.yml +++ b/it/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 438dc9591d69d02d85a986387ae80b730552c3d6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:44 +0900 Subject: [PATCH 0938/1932] New translations surveys.yml (Portuguese) --- pt/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/pt/surveys.yml b/pt/surveys.yml index f437c01bf44..8642847436a 100644 --- a/pt/surveys.yml +++ b/pt/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 7323dfcb306b37a33cb6de783e4ffed7a51a15e3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:47 +0900 Subject: [PATCH 0939/1932] New translations common.yml (Russian) --- ru/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ru/common.yml b/ru/common.yml index 512b402adca..894c5fe6237 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 7f3be55bcad6cfdc8ac890c0e57956bca682e93e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:48 +0900 Subject: [PATCH 0940/1932] New translations surveys.yml (Russian) --- ru/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/ru/surveys.yml b/ru/surveys.yml index f437c01bf44..8642847436a 100644 --- a/ru/surveys.yml +++ b/ru/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 2cddc7926a530538206e43ebc9c4ab6473f31a4f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:49 +0900 Subject: [PATCH 0941/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sr/common.yml b/sr/common.yml index 512b402adca..894c5fe6237 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 7ebebefa05f231817fc1517c3a2c0ea77661efff Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:50 +0900 Subject: [PATCH 0942/1932] New translations surveys.yml (Serbian (Cyrillic)) --- sr/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/sr/surveys.yml b/sr/surveys.yml index f437c01bf44..8642847436a 100644 --- a/sr/surveys.yml +++ b/sr/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 058781ec6da38f5b8bd73cee37ea0286c7f9df6f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:51 +0900 Subject: [PATCH 0943/1932] New translations common.yml (Swedish) --- sv/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sv/common.yml b/sv/common.yml index 512b402adca..894c5fe6237 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 97720519d98a64307a6feec4cf1ee51a4bc8b25a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:52 +0900 Subject: [PATCH 0944/1932] New translations surveys.yml (Swedish) --- sv/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/sv/surveys.yml b/sv/surveys.yml index f437c01bf44..8642847436a 100644 --- a/sv/surveys.yml +++ b/sv/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From cf94b014cd92592cff0c4edefdfbe34595abee3c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:55 +0900 Subject: [PATCH 0945/1932] New translations common.yml (Turkish) --- tr/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tr/common.yml b/tr/common.yml index 512b402adca..894c5fe6237 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 623e9b8193e3cf6e0025c70423abc023be393d73 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:56 +0900 Subject: [PATCH 0946/1932] New translations surveys.yml (Turkish) --- tr/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/tr/surveys.yml b/tr/surveys.yml index f437c01bf44..8642847436a 100644 --- a/tr/surveys.yml +++ b/tr/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From e7fb88e3461abfc247946a3fd79afbc6002bc977 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:57 +0900 Subject: [PATCH 0947/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/uk/common.yml b/uk/common.yml index 512b402adca..894c5fe6237 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From c99d678a3977de447521b9a0ea723f65ac048bec Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:58 +0900 Subject: [PATCH 0948/1932] New translations surveys.yml (Italian) --- it/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/it/surveys.yml b/it/surveys.yml index f437c01bf44..8642847436a 100644 --- a/it/surveys.yml +++ b/it/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 0e0d6b5e2b70d24b64255b4f13fae1fccf2a1c50 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:24:59 +0900 Subject: [PATCH 0949/1932] New translations surveys.yml (Hungarian) --- hu/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/hu/surveys.yml b/hu/surveys.yml index f437c01bf44..8642847436a 100644 --- a/hu/surveys.yml +++ b/hu/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 96b8fe9d239c7f84728a6dc2021766fb4abf593a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:00 +0900 Subject: [PATCH 0950/1932] New translations surveys.yml (Romanian) --- ro/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/ro/surveys.yml b/ro/surveys.yml index f437c01bf44..8642847436a 100644 --- a/ro/surveys.yml +++ b/ro/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 29835cba3ddd1771d9c65bd465000f53331b241b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:01 +0900 Subject: [PATCH 0951/1932] New translations common.yml (Czech) --- cs/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/cs/common.yml b/cs/common.yml index 512b402adca..894c5fe6237 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 779ed0fb63ec4c40704dce42fa6a4c3057f01ff3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:02 +0900 Subject: [PATCH 0952/1932] New translations common.yml (French) --- fr/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fr/common.yml b/fr/common.yml index 512b402adca..894c5fe6237 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 72b94826258cf2023a70e8d8be4db1c3e975d475 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:03 +0900 Subject: [PATCH 0953/1932] New translations surveys.yml (French) --- fr/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/fr/surveys.yml b/fr/surveys.yml index f437c01bf44..8642847436a 100644 --- a/fr/surveys.yml +++ b/fr/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 58f094688c77eca0b6d96cd53f129a97b1f3af8c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:04 +0900 Subject: [PATCH 0954/1932] New translations common.yml (Spanish) --- es/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/es/common.yml b/es/common.yml index 512b402adca..894c5fe6237 100644 --- a/es/common.yml +++ b/es/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From bb339fd9eeabac9678707ebff0cb19fa6e00c27c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:05 +0900 Subject: [PATCH 0955/1932] New translations surveys.yml (Spanish) --- es/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/es/surveys.yml b/es/surveys.yml index f437c01bf44..8642847436a 100644 --- a/es/surveys.yml +++ b/es/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 3224db76e5bae2ad3a83458a8c120f125ea797ed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:08 +0900 Subject: [PATCH 0956/1932] New translations common.yml (Afrikaans) --- af/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/af/common.yml b/af/common.yml index 512b402adca..894c5fe6237 100644 --- a/af/common.yml +++ b/af/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 0ae8360c7192f7b8f4696370b1225d5539846655 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:10 +0900 Subject: [PATCH 0957/1932] New translations surveys.yml (Afrikaans) --- af/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/af/surveys.yml b/af/surveys.yml index f437c01bf44..8642847436a 100644 --- a/af/surveys.yml +++ b/af/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 7f505159b305e8142bf4de72bd5725cc7a68672b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:11 +0900 Subject: [PATCH 0958/1932] New translations common.yml (Arabic) --- ar/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ar/common.yml b/ar/common.yml index 512b402adca..894c5fe6237 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 2871eaf473c973e978c24b56e7459e450a26ace6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:12 +0900 Subject: [PATCH 0959/1932] New translations surveys.yml (Arabic) --- ar/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/ar/surveys.yml b/ar/surveys.yml index f437c01bf44..8642847436a 100644 --- a/ar/surveys.yml +++ b/ar/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 7b345dacf292702c72380a248ed22befd2daeaff Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:13 +0900 Subject: [PATCH 0960/1932] New translations common.yml (Catalan) --- ca/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ca/common.yml b/ca/common.yml index 512b402adca..894c5fe6237 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 63813966db29a3033cdd1e9192d0159cede1c3d0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:14 +0900 Subject: [PATCH 0961/1932] New translations surveys.yml (Catalan) --- ca/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/ca/surveys.yml b/ca/surveys.yml index f437c01bf44..8642847436a 100644 --- a/ca/surveys.yml +++ b/ca/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 5d092e77efe0f65e015a1b837a3516cc0de41e07 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:15 +0900 Subject: [PATCH 0962/1932] New translations surveys.yml (Czech) --- cs/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/cs/surveys.yml b/cs/surveys.yml index f437c01bf44..8642847436a 100644 --- a/cs/surveys.yml +++ b/cs/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From bfc4ff405a353e5c6bab19c999936e2aa991f14d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:16 +0900 Subject: [PATCH 0963/1932] New translations common.yml (Hungarian) --- hu/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/hu/common.yml b/hu/common.yml index 512b402adca..894c5fe6237 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 31461e0624c8cd8b08cad1af2566dc9fc37293f3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:17 +0900 Subject: [PATCH 0964/1932] New translations common.yml (Danish) --- da/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/da/common.yml b/da/common.yml index 512b402adca..894c5fe6237 100644 --- a/da/common.yml +++ b/da/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 5726296ff99ae8638e045d25da23b9d49b74481b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:19 +0900 Subject: [PATCH 0965/1932] New translations surveys.yml (Danish) --- da/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/da/surveys.yml b/da/surveys.yml index f437c01bf44..8642847436a 100644 --- a/da/surveys.yml +++ b/da/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 29e609702ede65491f246be5ccf6acfca0e45fad Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:20 +0900 Subject: [PATCH 0966/1932] New translations common.yml (German) --- de/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/de/common.yml b/de/common.yml index 512b402adca..894c5fe6237 100644 --- a/de/common.yml +++ b/de/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 17c86a7955386df7fd705d2e23740b84daee8fd5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:21 +0900 Subject: [PATCH 0967/1932] New translations surveys.yml (German) --- de/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/de/surveys.yml b/de/surveys.yml index f437c01bf44..8642847436a 100644 --- a/de/surveys.yml +++ b/de/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 8aba3d2cab4313e102b60b1a7be724a52d682146 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:22 +0900 Subject: [PATCH 0968/1932] New translations common.yml (Greek) --- el/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/el/common.yml b/el/common.yml index 512b402adca..894c5fe6237 100644 --- a/el/common.yml +++ b/el/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 97e161d46759e9fe9092d96fed52bd8c9268e137 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:23 +0900 Subject: [PATCH 0969/1932] New translations surveys.yml (Greek) --- el/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/el/surveys.yml b/el/surveys.yml index f437c01bf44..8642847436a 100644 --- a/el/surveys.yml +++ b/el/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From a5288d0ba5521242d499a7b0e229f277bfe85e64 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:24 +0900 Subject: [PATCH 0970/1932] New translations common.yml (Finnish) --- fi/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fi/common.yml b/fi/common.yml index 512b402adca..894c5fe6237 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 7678f7b4d25bfd17fcc79fd5b08624b57be392dc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:25 +0900 Subject: [PATCH 0971/1932] New translations surveys.yml (Finnish) --- fi/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/fi/surveys.yml b/fi/surveys.yml index f437c01bf44..8642847436a 100644 --- a/fi/surveys.yml +++ b/fi/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From e285718f819b561f9f41471c5d7c73c0440bc4ac Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:26 +0900 Subject: [PATCH 0972/1932] New translations common.yml (Hebrew) --- he/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/he/common.yml b/he/common.yml index 512b402adca..894c5fe6237 100644 --- a/he/common.yml +++ b/he/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 5ce878ddde16e10aa0e9228a7aaf206651807499 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:26 +0900 Subject: [PATCH 0973/1932] New translations surveys.yml (Hebrew) --- he/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/he/surveys.yml b/he/surveys.yml index f437c01bf44..8642847436a 100644 --- a/he/surveys.yml +++ b/he/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 6a755db2f36ded5a3a4ad60db0e88686bbe86b1d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:27 +0900 Subject: [PATCH 0974/1932] New translations surveys.yml (Ukrainian) --- uk/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/uk/surveys.yml b/uk/surveys.yml index f437c01bf44..8642847436a 100644 --- a/uk/surveys.yml +++ b/uk/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From a9c7f0971c0ef5061aa9e221ca0758e7d59c4dea Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:29 +0900 Subject: [PATCH 0975/1932] New translations common.yml (Chinese Simplified) --- zh/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/zh/common.yml b/zh/common.yml index 512b402adca..894c5fe6237 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 7da1633b1b2c4727cf93cb6262dca317a4301bfd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:30 +0900 Subject: [PATCH 0976/1932] New translations homepage.yml (English) --- en/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/en/homepage.yml b/en/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/en/homepage.yml +++ b/en/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 99601f90d7334140929081c37fd7eb745d70bad3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:31 +0900 Subject: [PATCH 0977/1932] New translations homepage.yml (Polish) --- pl/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/pl/homepage.yml b/pl/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/pl/homepage.yml +++ b/pl/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From d4aa5c2dabcdb4d722eb07b91b3b8316d41a2d12 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:31 +0900 Subject: [PATCH 0978/1932] New translations homepage.yml (Portuguese) --- pt/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/pt/homepage.yml b/pt/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/pt/homepage.yml +++ b/pt/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 2e2e6b1ebd62075231d795a7141e4f7b6eb7f642 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:32 +0900 Subject: [PATCH 0979/1932] New translations homepage.yml (Russian) --- ru/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/ru/homepage.yml b/ru/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/ru/homepage.yml +++ b/ru/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From f904a862be24e77a23c859c14cb6fc74de8b4d2c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:33 +0900 Subject: [PATCH 0980/1932] New translations homepage.yml (Serbian (Cyrillic)) --- sr/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/sr/homepage.yml b/sr/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/sr/homepage.yml +++ b/sr/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From d73c05c571de0a622e4ed0cc3ceadfd3edbf83cc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:34 +0900 Subject: [PATCH 0981/1932] New translations homepage.yml (Swedish) --- sv/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/sv/homepage.yml b/sv/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/sv/homepage.yml +++ b/sv/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 61b30aeac266efbcc288bdf732155d3cb2593c7d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:35 +0900 Subject: [PATCH 0982/1932] New translations homepage.yml (Turkish) --- tr/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/tr/homepage.yml b/tr/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/tr/homepage.yml +++ b/tr/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 012d4c2edc905387d567f93b38b1d3a8dcde203f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:36 +0900 Subject: [PATCH 0983/1932] New translations homepage.yml (Ukrainian) --- uk/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/uk/homepage.yml b/uk/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/uk/homepage.yml +++ b/uk/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 593ab1add81b5cf6e2072051daee3b00dd7ae7dd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:37 +0900 Subject: [PATCH 0984/1932] New translations homepage.yml (Chinese Simplified) --- zh/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/zh/homepage.yml b/zh/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/zh/homepage.yml +++ b/zh/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 8b9c019da741ae9c7a73215076117f22c563e4c8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:39 +0900 Subject: [PATCH 0985/1932] New translations homepage.yml (Vietnamese) --- vi/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/vi/homepage.yml b/vi/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/vi/homepage.yml +++ b/vi/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From d890e559a506878c76610a476767463ac0012e62 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:39 +0900 Subject: [PATCH 0986/1932] New translations homepage.yml (Dutch) --- nl/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/nl/homepage.yml b/nl/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/nl/homepage.yml +++ b/nl/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From a0be6821fd9c95e0b07f9ac5c2350eb01f7c20d1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:41 +0900 Subject: [PATCH 0987/1932] New translations accounts.yml (Romanian) --- ro/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ro/accounts.yml b/ro/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/ro/accounts.yml +++ b/ro/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From dfcd826e18c7d8c309cb66976dcc4d1e0db759f2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:42 +0900 Subject: [PATCH 0988/1932] New translations state_of_css.yml (Romanian) --- ro/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ro/state_of_css.yml b/ro/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/ro/state_of_css.yml +++ b/ro/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 750f44b51a3c40ee0f0c08fc2b368a2bdf75eb24 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:43 +0900 Subject: [PATCH 0989/1932] New translations state_of_js.yml (Romanian) --- ro/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/ro/state_of_js.yml b/ro/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/ro/state_of_js.yml +++ b/ro/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 31495d507faebae097a200c76a6259a07a5d0b2e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:44 +0900 Subject: [PATCH 0990/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From af454fe571d4f3602b6cbae7c1bad3bbdd93f7fd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:45 +0900 Subject: [PATCH 0991/1932] New translations accounts.yml (French) --- fr/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fr/accounts.yml b/fr/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/fr/accounts.yml +++ b/fr/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From d03edd3e4fb7cbd54a97f49148437a07ab1a9a78 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:46 +0900 Subject: [PATCH 0992/1932] New translations state_of_css.yml (French) --- fr/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fr/state_of_css.yml b/fr/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/fr/state_of_css.yml +++ b/fr/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From c317c8973b8be5b3d8d9b15836e861c77846021f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:47 +0900 Subject: [PATCH 0993/1932] New translations state_of_js.yml (French) --- fr/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/fr/state_of_js.yml b/fr/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/fr/state_of_js.yml +++ b/fr/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From edc3ee36027e8517238df93dac7bb7c7a63207b1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:48 +0900 Subject: [PATCH 0994/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 28b6c48a031fe0f6fc0dad88937cfa5dc2e95c5c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:49 +0900 Subject: [PATCH 0995/1932] New translations accounts.yml (Spanish) --- es/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/es/accounts.yml b/es/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/es/accounts.yml +++ b/es/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From f5d128392014be9e755c137df2c9f34a2edffcc0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:50 +0900 Subject: [PATCH 0996/1932] New translations homepage.yml (Norwegian) --- no/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/no/homepage.yml b/no/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/no/homepage.yml +++ b/no/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 3111b850a70e532475a7c0442e016cb05d377579 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:51 +0900 Subject: [PATCH 0997/1932] New translations homepage.yml (Korean) --- ko/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/ko/homepage.yml b/ko/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/ko/homepage.yml +++ b/ko/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From c2f91dcf2c6992392abafe3cc9c8e32953d63e03 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:52 +0900 Subject: [PATCH 0998/1932] New translations surveys.yml (Chinese Simplified) --- zh/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/zh/surveys.yml b/zh/surveys.yml index f437c01bf44..8642847436a 100644 --- a/zh/surveys.yml +++ b/zh/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 5261da8ba6e656fd400dd27fbe9aee66d5758ce5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:53 +0900 Subject: [PATCH 0999/1932] New translations homepage.yml (Spanish) --- es/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/es/homepage.yml b/es/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/es/homepage.yml +++ b/es/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 74ea25fef5b43ee5c6a2ea5839c74b698bbff128 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:56 +0900 Subject: [PATCH 1000/1932] New translations common.yml (English) --- en/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/en/common.yml b/en/common.yml index 512b402adca..894c5fe6237 100644 --- a/en/common.yml +++ b/en/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From 962513d98ce129b72940719d548147246610b305 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:57 +0900 Subject: [PATCH 1001/1932] New translations surveys.yml (English) --- en/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/en/surveys.yml b/en/surveys.yml index f437c01bf44..8642847436a 100644 --- a/en/surveys.yml +++ b/en/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 6f33778ee52c47dc3dfa81bce41b1f2a6039b886 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:58 +0900 Subject: [PATCH 1002/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/vi/common.yml b/vi/common.yml index 512b402adca..894c5fe6237 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -237,6 +237,9 @@ translations: - key: general.charts_nivo t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics - ########################################################################### #Nav From c9d2e9683e35b80726f2dcd87d39594b697614e0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:25:59 +0900 Subject: [PATCH 1003/1932] New translations surveys.yml (Vietnamese) --- vi/surveys.yml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/vi/surveys.yml b/vi/surveys.yml index f437c01bf44..8642847436a 100644 --- a/vi/surveys.yml +++ b/vi/surveys.yml @@ -10,6 +10,15 @@ translations: - key: general.global_nav t: Global + - + key: general.survey_status_preview + t: Preview + - + key: general.survey_status_open + t: Open + - + key: general.survey_status_closed + t: Closed - ########################################################################### #Accounts @@ -123,3 +132,15 @@ translations: - key: bracket.cancel t: Cancel + - + ########################################################################### + #Response + ########################################################################### + key: response.completion + t: '{completion}% completed' + - + key: response.details + t: Started on {startedAt}, {completion}% completed. + - + key: response.view_results + t: View Results From 328f1007f24c4ecb2958b698a1add0c1ac3054bc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:02 +0900 Subject: [PATCH 1004/1932] New translations homepage.yml (Romanian) --- ro/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/ro/homepage.yml b/ro/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/ro/homepage.yml +++ b/ro/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From d930bb4b709328a6c37bcb0ed334ed52875d1551 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:03 +0900 Subject: [PATCH 1005/1932] New translations homepage.yml (French) --- fr/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/fr/homepage.yml b/fr/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/fr/homepage.yml +++ b/fr/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From d9c94d9ad7e25b10addb0b18a61d85b3473dee5b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:04 +0900 Subject: [PATCH 1006/1932] New translations homepage.yml (Afrikaans) --- af/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/af/homepage.yml b/af/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/af/homepage.yml +++ b/af/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 9c72d5d7d3192cfa14d56a2e53eb2c5804c1cf3e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:04 +0900 Subject: [PATCH 1007/1932] New translations homepage.yml (Japanese) --- ja/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/ja/homepage.yml b/ja/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/ja/homepage.yml +++ b/ja/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From a53d2a6378ad6fa3e0650e588802f788aba7ae67 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:05 +0900 Subject: [PATCH 1008/1932] New translations homepage.yml (Arabic) --- ar/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/ar/homepage.yml b/ar/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/ar/homepage.yml +++ b/ar/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From cf1289a90cc0e158598e8ea95583866100c3430d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:06 +0900 Subject: [PATCH 1009/1932] New translations homepage.yml (Catalan) --- ca/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/ca/homepage.yml b/ca/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/ca/homepage.yml +++ b/ca/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From f35759dea560223ca06a89197029a04eb0649a68 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:07 +0900 Subject: [PATCH 1010/1932] New translations homepage.yml (Czech) --- cs/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/cs/homepage.yml b/cs/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/cs/homepage.yml +++ b/cs/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From ac65c78bbaf29a6cb49e5ddbe665c579caa0a016 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:08 +0900 Subject: [PATCH 1011/1932] New translations homepage.yml (Danish) --- da/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/da/homepage.yml b/da/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/da/homepage.yml +++ b/da/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 5cdb43684fe096412efc76c17454dd0548ead96f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:11 +0900 Subject: [PATCH 1012/1932] New translations homepage.yml (German) --- de/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/de/homepage.yml b/de/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/de/homepage.yml +++ b/de/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 980a49810c7c38903cfc590486f86d92e814e4be Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:11 +0900 Subject: [PATCH 1013/1932] New translations homepage.yml (Greek) --- el/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/el/homepage.yml b/el/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/el/homepage.yml +++ b/el/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 914ad9bc85f8b7a89ca75ba54e2d32f3e3188ec6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:13 +0900 Subject: [PATCH 1014/1932] New translations homepage.yml (Finnish) --- fi/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/fi/homepage.yml b/fi/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/fi/homepage.yml +++ b/fi/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 8c5e5e82e2baa1f96e72f336afc5001f4b72b57c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:13 +0900 Subject: [PATCH 1015/1932] New translations homepage.yml (Hebrew) --- he/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/he/homepage.yml b/he/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/he/homepage.yml +++ b/he/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 8070e5dfb4473b79dc471e353e51b08836f99ae0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:15 +0900 Subject: [PATCH 1016/1932] New translations homepage.yml (Hungarian) --- hu/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/hu/homepage.yml b/hu/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/hu/homepage.yml +++ b/hu/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From ea3470479d9e9c2677d3b0f1cc88ee53f70ee55e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:16 +0900 Subject: [PATCH 1017/1932] New translations homepage.yml (Italian) --- it/homepage.yml | 33 +++++++++++++++++++++++++++------ 1 file changed, 27 insertions(+), 6 deletions(-) diff --git a/it/homepage.yml b/it/homepage.yml index 6a83e7939b5..3996a6b5a3f 100644 --- a/it/homepage.yml +++ b/it/homepage.yml @@ -41,10 +41,31 @@ translations: key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: author.sacha.bio - t: > - Creator of the [Nivo](http://nivo.rocks/) JavaScript data visualization library as well as [Mozaik](http://mozaik.rocks/), a tool for building beautiful dashboards. + key: homepage.other_surveys + t: 'Other Surveys:' - - key: author.raphael.bio - t: > - Creator of the [Sidebar](http://sidebar.io) daily newsletter and [VulcanJS](http://vulcanjs.org), a React+GraphQL open-source framework. + key: homepage.survey_open_now + t: Currently Open + - + key: homepage.current_survey + t: Current Survey + - + key: homepage.past_surveys + t: Past Surveys + - + key: homepage.view_questions + t: View Questions + - + #newsletter + key: homepage.newsletter.email + t: Your Email + - + key: homepage.newsletter.submit + t: Notify Me + - + #languages + key: languages.available_languages + t: 'Available languages:' + - + key: languages.help_us_translate + t: Help us translate the survey in your language. From 9a6a00f4f635bdd19a5429ab759372d398d1fdd3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:17 +0900 Subject: [PATCH 1018/1932] New translations state_of_css.yml (Spanish) --- es/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/es/state_of_css.yml b/es/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/es/state_of_css.yml +++ b/es/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 56cc2de033b2be01473a540cba265eb7a0f146b6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:18 +0900 Subject: [PATCH 1019/1932] New translations state_of_js.yml (Spanish) --- es/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/es/state_of_js.yml b/es/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/es/state_of_js.yml +++ b/es/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 57e1df5cfa15062e7bd213f0782d7e84255e90c4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:19 +0900 Subject: [PATCH 1020/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 3de60b763dbae4d40051784bd249ae11dcffaaed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:20 +0900 Subject: [PATCH 1021/1932] New translations state_of_js.yml (Greek) --- el/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/el/state_of_js.yml b/el/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/el/state_of_js.yml +++ b/el/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 01a32086c0d369336a702b79ee98ab26ef68b97c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:21 +0900 Subject: [PATCH 1022/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 1a7c338fc776102406849e8dcc8ae0c9bc4b9ed1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:21 +0900 Subject: [PATCH 1023/1932] New translations accounts.yml (Finnish) --- fi/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fi/accounts.yml b/fi/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/fi/accounts.yml +++ b/fi/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 34282bbe09aae8c6e8b0e55e5a27a97c6c710d1e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:22 +0900 Subject: [PATCH 1024/1932] New translations state_of_css.yml (Finnish) --- fi/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fi/state_of_css.yml b/fi/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/fi/state_of_css.yml +++ b/fi/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 478a56e0080a62ac7c43a3b0da868afc4048a3ac Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:24 +0900 Subject: [PATCH 1025/1932] New translations state_of_js.yml (Finnish) --- fi/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/fi/state_of_js.yml b/fi/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/fi/state_of_js.yml +++ b/fi/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 909b91c83410a32a4f1fb1d333b936fec20fee61 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:25 +0900 Subject: [PATCH 1026/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 7731a003cb69a0916272ca5c10ff1f26e5ec7e0a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:26 +0900 Subject: [PATCH 1027/1932] New translations accounts.yml (Hebrew) --- he/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/he/accounts.yml b/he/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/he/accounts.yml +++ b/he/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From c6a9e77f1d791582cb75a6af9138107a481793be Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:27 +0900 Subject: [PATCH 1028/1932] New translations state_of_css.yml (Hebrew) --- he/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/he/state_of_css.yml b/he/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/he/state_of_css.yml +++ b/he/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 33c8e45baac1abf74fa5aaf62c96113ffccb910f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:28 +0900 Subject: [PATCH 1029/1932] New translations state_of_js.yml (Hebrew) --- he/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/he/state_of_js.yml b/he/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/he/state_of_js.yml +++ b/he/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 42435bc614a05eef7329da7c37da3dd1bdc07d18 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:29 +0900 Subject: [PATCH 1030/1932] New translations accounts.yml (Hungarian) --- hu/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/hu/accounts.yml b/hu/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/hu/accounts.yml +++ b/hu/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 483397964ed15e0eda31150f47bdf7328890d4d1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:30 +0900 Subject: [PATCH 1031/1932] New translations accounts.yml (Greek) --- el/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/el/accounts.yml b/el/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/el/accounts.yml +++ b/el/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 20ebd53257f769c096d353a1a9416eafdd0178e0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:33 +0900 Subject: [PATCH 1032/1932] New translations state_of_css.yml (Hungarian) --- hu/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hu/state_of_css.yml b/hu/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/hu/state_of_css.yml +++ b/hu/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 7e75b4e18125d26f46035d483e36f1311ffc453c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:34 +0900 Subject: [PATCH 1033/1932] New translations state_of_js.yml (Hungarian) --- hu/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/hu/state_of_js.yml b/hu/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/hu/state_of_js.yml +++ b/hu/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From eb7a1700d3caabba289a85cf60d4c6c4ead689e6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:35 +0900 Subject: [PATCH 1034/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 087071d5c881107ead29ef1f6028bc9fde9eb9ee Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:36 +0900 Subject: [PATCH 1035/1932] New translations accounts.yml (Italian) --- it/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/it/accounts.yml b/it/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/it/accounts.yml +++ b/it/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 88e37deffb11ddfe4411217934fa6f916b2775cd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:37 +0900 Subject: [PATCH 1036/1932] New translations state_of_css.yml (Italian) --- it/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/it/state_of_css.yml b/it/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/it/state_of_css.yml +++ b/it/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 3921ce68ba43683465c772612399d295238a4361 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:38 +0900 Subject: [PATCH 1037/1932] New translations state_of_js.yml (Italian) --- it/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/it/state_of_js.yml b/it/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/it/state_of_js.yml +++ b/it/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From d480a2d61d1f24771bda0de3feb448f74a5e7aa4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:39 +0900 Subject: [PATCH 1038/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 8fd81f59932246ec03750659652f44ae33c75d90 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:41 +0900 Subject: [PATCH 1039/1932] New translations accounts.yml (Japanese) --- ja/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ja/accounts.yml b/ja/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/ja/accounts.yml +++ b/ja/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 47dd676c58048a24370e9f584180d236284aab8d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:43 +0900 Subject: [PATCH 1040/1932] New translations state_of_css.yml (Japanese) --- ja/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ja/state_of_css.yml b/ja/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/ja/state_of_css.yml +++ b/ja/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From d21cecd693f4595b0f503d9c7b0531eaebfb8a01 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:44 +0900 Subject: [PATCH 1041/1932] New translations state_of_js.yml (Japanese) --- ja/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/ja/state_of_js.yml b/ja/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/ja/state_of_js.yml +++ b/ja/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 9f609458ff32b6106f36d511eb9f56f0bf423adb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:45 +0900 Subject: [PATCH 1042/1932] New translations state_of_css.yml (Greek) --- el/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/el/state_of_css.yml b/el/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/el/state_of_css.yml +++ b/el/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 05acec3426ed0367d5e435617c27ef777800c6f7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:46 +0900 Subject: [PATCH 1043/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 019fe2196a7fd958d9c5d75e292530ce59f1b0bb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:47 +0900 Subject: [PATCH 1044/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 9900e9275c3747a6765e3c17ce289c1e081718dd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:48 +0900 Subject: [PATCH 1045/1932] New translations state_of_js.yml (Catalan) --- ca/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/ca/state_of_js.yml b/ca/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/ca/state_of_js.yml +++ b/ca/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From a17b16bd95bd92134b72cd4fd9b07491eb4a4c17 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:49 +0900 Subject: [PATCH 1046/1932] New translations accounts.yml (Afrikaans) --- af/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/af/accounts.yml b/af/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/af/accounts.yml +++ b/af/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 486f6abe2db54844f5db2ebc35c85cf1ff4dbdd3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:51 +0900 Subject: [PATCH 1047/1932] New translations state_of_css.yml (Afrikaans) --- af/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/af/state_of_css.yml b/af/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/af/state_of_css.yml +++ b/af/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From e6d69f790e2db71a4dd4aee5b4e85496da93c549 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:52 +0900 Subject: [PATCH 1048/1932] New translations state_of_js.yml (Afrikaans) --- af/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/af/state_of_js.yml b/af/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/af/state_of_js.yml +++ b/af/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From b5793f34a5b4bbb7ba5c84bd4eb28e3ade98f5af Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:53 +0900 Subject: [PATCH 1049/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 139d5ca45c0d26fe1d1d59f57d95f49f41b342b7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:53 +0900 Subject: [PATCH 1050/1932] New translations accounts.yml (Arabic) --- ar/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ar/accounts.yml b/ar/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/ar/accounts.yml +++ b/ar/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From caee42e7e58836e7a76730c6537563bbb3e22be9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:54 +0900 Subject: [PATCH 1051/1932] New translations state_of_css.yml (Arabic) --- ar/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ar/state_of_css.yml b/ar/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/ar/state_of_css.yml +++ b/ar/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From eb8913cae9d599d590f3222a18ee3b2b3ef606bb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:55 +0900 Subject: [PATCH 1052/1932] New translations state_of_js.yml (Arabic) --- ar/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/ar/state_of_js.yml b/ar/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/ar/state_of_js.yml +++ b/ar/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 330a48988ce1c96d670e9aae4286ff183c822fa3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:56 +0900 Subject: [PATCH 1053/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 7b99084bf32cff3221d27d029eb7044c1b12ab54 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:57 +0900 Subject: [PATCH 1054/1932] New translations accounts.yml (Catalan) --- ca/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ca/accounts.yml b/ca/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/ca/accounts.yml +++ b/ca/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 84f595b84c643a1557752c81c5f2d0a60c37ea7d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:58 +0900 Subject: [PATCH 1055/1932] New translations state_of_css.yml (Catalan) --- ca/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ca/state_of_css.yml b/ca/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/ca/state_of_css.yml +++ b/ca/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From cc0086d310e9c71e817a69598f7df0c28488d73e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:26:59 +0900 Subject: [PATCH 1056/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 7ea587726cba139f52f1a0a1837acf4e88e0282f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:02 +0900 Subject: [PATCH 1057/1932] New translations state_of_js.yml (German) --- de/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/de/state_of_js.yml b/de/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/de/state_of_js.yml +++ b/de/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 73390cf46ce6761b47edbc602c680e0a8a98ee91 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:03 +0900 Subject: [PATCH 1058/1932] New translations accounts.yml (Czech) --- cs/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/cs/accounts.yml b/cs/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/cs/accounts.yml +++ b/cs/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From bedf35bdf8c473916103f041bc647b0d62512ffb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:04 +0900 Subject: [PATCH 1059/1932] New translations state_of_css.yml (Czech) --- cs/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cs/state_of_css.yml b/cs/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/cs/state_of_css.yml +++ b/cs/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From f65f2000cadd317c4f68d79a56d77778a41e5afb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:05 +0900 Subject: [PATCH 1060/1932] New translations state_of_js.yml (Czech) --- cs/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/cs/state_of_js.yml b/cs/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/cs/state_of_js.yml +++ b/cs/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 73a6c05aca87e88b0503faff7239e64a952d3b1e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:06 +0900 Subject: [PATCH 1061/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 1d0564b66567dc86de406672700f50f708ccd1f0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:07 +0900 Subject: [PATCH 1062/1932] New translations accounts.yml (Danish) --- da/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/da/accounts.yml b/da/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/da/accounts.yml +++ b/da/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 8d42cd152d12123b3be1b4a36b20cb69d9c1a82a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:09 +0900 Subject: [PATCH 1063/1932] New translations state_of_css.yml (Danish) --- da/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/da/state_of_css.yml b/da/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/da/state_of_css.yml +++ b/da/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 494f3ebec6cdcc59ebe96ae5f865e52ed48527e5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:10 +0900 Subject: [PATCH 1064/1932] New translations state_of_js.yml (Danish) --- da/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/da/state_of_js.yml b/da/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/da/state_of_js.yml +++ b/da/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 18cc66cf85e48366f71b73e14c53811fb7de5e49 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:11 +0900 Subject: [PATCH 1065/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From d09c10cd0266a32a04813387c889f072abd5dbf2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:12 +0900 Subject: [PATCH 1066/1932] New translations accounts.yml (German) --- de/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/de/accounts.yml b/de/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/de/accounts.yml +++ b/de/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From e25939f034ba5cb3ca00fc999fe63241e084ecb0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:13 +0900 Subject: [PATCH 1067/1932] New translations state_of_css.yml (German) --- de/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/de/state_of_css.yml b/de/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/de/state_of_css.yml +++ b/de/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From c8876748be3c7775389238598ef8563b9b9ed457 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:14 +0900 Subject: [PATCH 1068/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 3a2982fc4ef8141924b4c4e63a1eb0ca917baf6a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:15 +0900 Subject: [PATCH 1069/1932] New translations accounts.yml (Korean) --- ko/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ko/accounts.yml b/ko/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/ko/accounts.yml +++ b/ko/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 4c385e829c83bff74668d7519d56dcabe41bab5b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:16 +0900 Subject: [PATCH 1070/1932] New translations state_of_css.yml (Ukrainian) --- uk/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/uk/state_of_css.yml b/uk/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/uk/state_of_css.yml +++ b/uk/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 2a3ca7e33da88f4a9536c31c0502d72bffc37356 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:17 +0900 Subject: [PATCH 1071/1932] New translations accounts.yml (Swedish) --- sv/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sv/accounts.yml b/sv/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/sv/accounts.yml +++ b/sv/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 63f62b7c600336ab1adcc0819abead2bf6a8f664 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:18 +0900 Subject: [PATCH 1072/1932] New translations state_of_css.yml (Swedish) --- sv/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sv/state_of_css.yml b/sv/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/sv/state_of_css.yml +++ b/sv/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From d8c8649aff6f90b20a3adc18f87ed60ab3ebaac6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:19 +0900 Subject: [PATCH 1073/1932] New translations state_of_js.yml (Swedish) --- sv/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/sv/state_of_js.yml b/sv/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/sv/state_of_js.yml +++ b/sv/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 0c714f07bd11c61055102f042299890f93a780da Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:20 +0900 Subject: [PATCH 1074/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From f11de0caaecadd56109c213966fe3dbaa82039ee Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:21 +0900 Subject: [PATCH 1075/1932] New translations accounts.yml (Turkish) --- tr/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tr/accounts.yml b/tr/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/tr/accounts.yml +++ b/tr/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From aa1600b1ca56c621d58139d4bb2c5dbdc1f36746 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:22 +0900 Subject: [PATCH 1076/1932] New translations state_of_css.yml (Turkish) --- tr/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tr/state_of_css.yml b/tr/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/tr/state_of_css.yml +++ b/tr/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From efa1e53a193177c32a40047debb9424a2ba537bc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:23 +0900 Subject: [PATCH 1077/1932] New translations state_of_js.yml (Turkish) --- tr/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/tr/state_of_js.yml b/tr/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/tr/state_of_js.yml +++ b/tr/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 8e1d782bcb07e61267b39bf4861df25e9fddac75 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:24 +0900 Subject: [PATCH 1078/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 34f89773fa0672778612613574e246ca9a584023 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:25 +0900 Subject: [PATCH 1079/1932] New translations accounts.yml (Ukrainian) --- uk/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/uk/accounts.yml b/uk/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/uk/accounts.yml +++ b/uk/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 5c18e5c398ead48305477e8d619027be1710b464 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:26 +0900 Subject: [PATCH 1080/1932] New translations state_of_js.yml (Ukrainian) --- uk/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/uk/state_of_js.yml b/uk/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/uk/state_of_js.yml +++ b/uk/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From d452df5ee97fef2c5df5b797783e47b274fc2fad Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:27 +0900 Subject: [PATCH 1081/1932] New translations state_of_js.yml (Serbian (Cyrillic)) --- sr/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/sr/state_of_js.yml b/sr/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/sr/state_of_js.yml +++ b/sr/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From b83c46f404049068af086c2d8a3394061f570199 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:28 +0900 Subject: [PATCH 1082/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 8eb5a3359c3141752d7d07b27e26e2b23e7e28aa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:29 +0900 Subject: [PATCH 1083/1932] New translations accounts.yml (Chinese Simplified) --- zh/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/zh/accounts.yml b/zh/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/zh/accounts.yml +++ b/zh/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From baaa3cffab301f7622a6f0743a2883e50290eb89 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:30 +0900 Subject: [PATCH 1084/1932] New translations state_of_css.yml (Chinese Simplified) --- zh/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh/state_of_css.yml b/zh/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/zh/state_of_css.yml +++ b/zh/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From b5d2f1deecf639c7b4cd46d54b070d3c6712e0b3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:31 +0900 Subject: [PATCH 1085/1932] New translations state_of_js.yml (Chinese Simplified) --- zh/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/zh/state_of_js.yml b/zh/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/zh/state_of_js.yml +++ b/zh/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 2ab593dbc782a05b6a6c26f1867f08bf0ff73237 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:32 +0900 Subject: [PATCH 1086/1932] New translations state_of_graphql.yml (Chinese Simplified) --- zh/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 9ac6468e0e099682c0f7677f4abd01158ed0e47d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:36 +0900 Subject: [PATCH 1087/1932] New translations accounts.yml (English) --- en/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/en/accounts.yml b/en/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/en/accounts.yml +++ b/en/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 9904ef061bd10cf8178b527743352a06be7240e8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:37 +0900 Subject: [PATCH 1088/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 3e4dbd567d16485074158f48ffc011589d069199 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:38 +0900 Subject: [PATCH 1089/1932] New translations state_of_css.yml (Serbian (Cyrillic)) --- sr/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sr/state_of_css.yml b/sr/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/sr/state_of_css.yml +++ b/sr/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 3b84709690e4aa4d71b621166402a9929b26e76a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:39 +0900 Subject: [PATCH 1090/1932] New translations state_of_css.yml (Korean) --- ko/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ko/state_of_css.yml b/ko/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/ko/state_of_css.yml +++ b/ko/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 4a72efcead8c63246deb6230966ccaa1aa85efc7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:40 +0900 Subject: [PATCH 1091/1932] New translations accounts.yml (Polish) --- pl/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pl/accounts.yml b/pl/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/pl/accounts.yml +++ b/pl/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 5edba99a7a5a146b44ad60f89f012a2cfbf104f2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:41 +0900 Subject: [PATCH 1092/1932] New translations state_of_js.yml (Korean) --- ko/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/ko/state_of_js.yml b/ko/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/ko/state_of_js.yml +++ b/ko/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 9d3a8835ee0be5714eba8f642a86d47d3964124d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:42 +0900 Subject: [PATCH 1093/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From fd645ec8462d52fecbb474c0f3f0d88801ea4c8a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:43 +0900 Subject: [PATCH 1094/1932] New translations accounts.yml (Dutch) --- nl/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/nl/accounts.yml b/nl/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/nl/accounts.yml +++ b/nl/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 995115f18e7ba4b3e4abb2293e7c090ed4fbff5c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:44 +0900 Subject: [PATCH 1095/1932] New translations state_of_css.yml (Dutch) --- nl/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nl/state_of_css.yml b/nl/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/nl/state_of_css.yml +++ b/nl/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From af16defebeb93bb9ab3ec81cc69062762a7641a3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:44 +0900 Subject: [PATCH 1096/1932] New translations state_of_js.yml (Dutch) --- nl/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/nl/state_of_js.yml b/nl/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/nl/state_of_js.yml +++ b/nl/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 55ea61e008357c8379101995abc07fc8311ebb92 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:46 +0900 Subject: [PATCH 1097/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 2cb11a6ba581e30be36ce6bdb1d2195627b1000c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:46 +0900 Subject: [PATCH 1098/1932] New translations accounts.yml (Norwegian) --- no/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/no/accounts.yml b/no/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/no/accounts.yml +++ b/no/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From cc430f6db6b9c9c58037c1da92a825f7f3cd26bb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:47 +0900 Subject: [PATCH 1099/1932] New translations state_of_css.yml (Norwegian) --- no/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/no/state_of_css.yml b/no/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/no/state_of_css.yml +++ b/no/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From c5f3cd78d91534ae3dc33294e779b23bd6f43695 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:48 +0900 Subject: [PATCH 1100/1932] New translations state_of_js.yml (Norwegian) --- no/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/no/state_of_js.yml b/no/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/no/state_of_js.yml +++ b/no/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 6f0c9e9e9e1693a1a5aa516fac3eaa59e86f215b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:49 +0900 Subject: [PATCH 1101/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 4ee432a0f8d78ce72624a7f4f0b93e87cdfe4220 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:50 +0900 Subject: [PATCH 1102/1932] New translations state_of_css.yml (Polish) --- pl/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pl/state_of_css.yml b/pl/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/pl/state_of_css.yml +++ b/pl/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 6eb318821e76a766582429601e71f5e58f27c47e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:51 +0900 Subject: [PATCH 1103/1932] New translations accounts.yml (Serbian (Cyrillic)) --- sr/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sr/accounts.yml b/sr/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/sr/accounts.yml +++ b/sr/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From f5a53004ca14c1b98fccadf7924cee5d7798de2d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:53 +0900 Subject: [PATCH 1104/1932] New translations state_of_js.yml (Polish) --- pl/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/pl/state_of_js.yml b/pl/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/pl/state_of_js.yml +++ b/pl/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 77b045f524df9b6be7edd66e38053897c1288bc4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:53 +0900 Subject: [PATCH 1105/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 027a5aa4ffc1ef4da40d0da376316650b7cb2613 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:54 +0900 Subject: [PATCH 1106/1932] New translations accounts.yml (Portuguese) --- pt/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pt/accounts.yml b/pt/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/pt/accounts.yml +++ b/pt/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 16a64768fe71d919860663937815d2b6537d7e1d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:55 +0900 Subject: [PATCH 1107/1932] New translations state_of_css.yml (Portuguese) --- pt/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pt/state_of_css.yml b/pt/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/pt/state_of_css.yml +++ b/pt/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From cd6ea04cff1dc162e122a3c299555c33d4a85a15 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:57 +0900 Subject: [PATCH 1108/1932] New translations state_of_js.yml (Portuguese) --- pt/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/pt/state_of_js.yml b/pt/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/pt/state_of_js.yml +++ b/pt/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From f198cc7e797d77214da171e7664786db86d2e5ab Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:58 +0900 Subject: [PATCH 1109/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From b302769092ab8150b2dd47aaccec1db7cbe7fe84 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:27:58 +0900 Subject: [PATCH 1110/1932] New translations accounts.yml (Russian) --- ru/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ru/accounts.yml b/ru/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/ru/accounts.yml +++ b/ru/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 366c239f46627eabc84a659e85a9db95c1634329 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:28:00 +0900 Subject: [PATCH 1111/1932] New translations state_of_css.yml (Russian) --- ru/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ru/state_of_css.yml b/ru/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/ru/state_of_css.yml +++ b/ru/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From b4ddc2a215e00c0f01e8931c0c58a0969309bfa9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:28:01 +0900 Subject: [PATCH 1112/1932] New translations state_of_js.yml (Russian) --- ru/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/ru/state_of_js.yml b/ru/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/ru/state_of_js.yml +++ b/ru/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 251d84126d91731417968cde03d441e9d43ccd4f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:28:02 +0900 Subject: [PATCH 1113/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From 36662597172f83168c6ffc29a46dd1c515e7dfa8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:28:03 +0900 Subject: [PATCH 1114/1932] New translations state_of_css.yml (English) --- en/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/state_of_css.yml b/en/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/en/state_of_css.yml +++ b/en/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 64cfad17b65693174ce6557dc85ab5dd36979c8f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:28:04 +0900 Subject: [PATCH 1115/1932] New translations state_of_js.yml (English) --- en/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/en/state_of_js.yml b/en/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/en/state_of_js.yml +++ b/en/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 68db5761a97908577033729b117dcd06026e25de Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:28:05 +0900 Subject: [PATCH 1116/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From a89a2a3dbb7bbfdb83bc617775bafdda3ee12b55 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:28:06 +0900 Subject: [PATCH 1117/1932] New translations accounts.yml (Vietnamese) --- vi/accounts.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/vi/accounts.yml b/vi/accounts.yml index 141b52d0949..ab7607801e3 100644 --- a/vi/accounts.yml +++ b/vi/accounts.yml @@ -119,3 +119,6 @@ translations: - key: accounts.token_verified t: Token verification successful, redirecting… + - + key: accounts.your_surveys + t: Your Surveys From 86a43305a88332ed21e8ca90c30d8256fb9bccb1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:28:07 +0900 Subject: [PATCH 1118/1932] New translations state_of_css.yml (Vietnamese) --- vi/state_of_css.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/vi/state_of_css.yml b/vi/state_of_css.yml index 89fa59e1cfc..2ef5c3308e5 100644 --- a/vi/state_of_css.yml +++ b/vi/state_of_css.yml @@ -6,7 +6,7 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_css2020 + key: general.state_of_css.intro t: > CSS is evolving faster than ever. @@ -14,7 +14,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - - key: general.results.description + key: general.state_of_css.description t: The annual survey about the latest trends in CSS. - ########################################################################### From 5e15fa0d8d94451e95b7389754378a2ddeddb30d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:28:08 +0900 Subject: [PATCH 1119/1932] New translations state_of_js.yml (Vietnamese) --- vi/state_of_js.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/vi/state_of_js.yml b/vi/state_of_js.yml index 2ecff184581..7649956d928 100644 --- a/vi/state_of_js.yml +++ b/vi/state_of_js.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_js2019 + key: general.state_of_js.intro t: > The JavaScript world could use a bit of classification. Since 2016, this survey has collected data from over 20,000 developers each year to identify current and upcoming trends. - Take the survey and help us find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. + - + key: general.state_of_js.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Sections From 34d6759d85f570ba638be92c42e9f1dc6edf2108 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 10 Jun 2022 15:28:09 +0900 Subject: [PATCH 1120/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index a305db3301d..7389f3cd337 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -6,13 +6,16 @@ translations: ########################################################################### #General ########################################################################### - key: general.survey_intro_graphql2022 + key: general.state_of_graphql.intro t: > When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.description + t: The annual survey of the JavaScript ecosystem. - ########################################################################### #Survey From f205499c5542f2122dc9c3db3b08e615dc520124 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:30:49 +0900 Subject: [PATCH 1121/1932] New translations homepage.yml (Romanian) --- ro/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/ro/homepage.yml b/ro/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/ro/homepage.yml +++ b/ro/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 1ddaac5e9645cd5803c2abf42ed66bf8342a16c1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:30:51 +0900 Subject: [PATCH 1122/1932] New translations state_of_js.yml (Spanish) --- es/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es/state_of_js.yml b/es/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/es/state_of_js.yml +++ b/es/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From a4c4bde3e4cb8171524afe2d55823e2a15818be6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:30:51 +0900 Subject: [PATCH 1123/1932] New translations homepage.yml (Vietnamese) --- vi/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/vi/homepage.yml b/vi/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/vi/homepage.yml +++ b/vi/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 18a92fc3f1d8d7d154337a8299f7a87cdaaa2193 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:30:52 +0900 Subject: [PATCH 1124/1932] New translations homepage.yml (Portuguese, Brazilian) --- pt/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/pt/homepage.yml b/pt/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/pt/homepage.yml +++ b/pt/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 788e5e0fc7a08bdfdf08bbd2fdfbc3670464499a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:30:54 +0900 Subject: [PATCH 1125/1932] New translations state_of_css.yml (Romanian) --- ro/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ro/state_of_css.yml b/ro/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/ro/state_of_css.yml +++ b/ro/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 3fe5fc85c99f99b92ae9d878111b92bc83190dbd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:30:54 +0900 Subject: [PATCH 1126/1932] New translations state_of_js.yml (Romanian) --- ro/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ro/state_of_js.yml b/ro/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/ro/state_of_js.yml +++ b/ro/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From b1a618f39192b80efcf396df3088b9db8f106055 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:30:56 +0900 Subject: [PATCH 1127/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From e6b0f3b5f3838efd2fdbca61e808a4c8777e71cc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:30:57 +0900 Subject: [PATCH 1128/1932] New translations state_of_css.yml (French) --- fr/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/state_of_css.yml b/fr/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/fr/state_of_css.yml +++ b/fr/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From eea32fe0445d0aced7740b0245bb20db72794e32 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:30:58 +0900 Subject: [PATCH 1129/1932] New translations state_of_js.yml (French) --- fr/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/state_of_js.yml b/fr/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/fr/state_of_js.yml +++ b/fr/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 707eaa0c4f713ac9b8e419ef2a1c55cfc77588b7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:30:59 +0900 Subject: [PATCH 1130/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From d25c545584c0891f3d1e1197a3a3e9f91dc8579f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:00 +0900 Subject: [PATCH 1131/1932] New translations state_of_css.yml (Spanish) --- es/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es/state_of_css.yml b/es/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/es/state_of_css.yml +++ b/es/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From a7a9d7de0ba1ba5bd032b8abdc5b25c15bbb38e0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:01 +0900 Subject: [PATCH 1132/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 218988d18324016e0530ec72a662c504a3767822 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:02 +0900 Subject: [PATCH 1133/1932] New translations homepage.yml (Chinese Traditional) --- zh/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/zh/homepage.yml b/zh/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/zh/homepage.yml +++ b/zh/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 639d1d219056ca30ffde1b789bfc2db0d806552e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:03 +0900 Subject: [PATCH 1134/1932] New translations state_of_css.yml (Afrikaans) --- af/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/af/state_of_css.yml b/af/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/af/state_of_css.yml +++ b/af/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From e0e5e37145f5745cf8ec67ea026a106f51354f80 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:04 +0900 Subject: [PATCH 1135/1932] New translations state_of_js.yml (Afrikaans) --- af/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/af/state_of_js.yml b/af/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/af/state_of_js.yml +++ b/af/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 776d915fe4195c3ce189a738a07d450d57f2760e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:06 +0900 Subject: [PATCH 1136/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From b9d598dce4b1c506d89001f3393daed76b3f1819 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:07 +0900 Subject: [PATCH 1137/1932] New translations state_of_css.yml (Arabic) --- ar/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ar/state_of_css.yml b/ar/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/ar/state_of_css.yml +++ b/ar/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From f75dec5aff828b2f59e9e690199545ae8b4fc184 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:08 +0900 Subject: [PATCH 1138/1932] New translations state_of_js.yml (Arabic) --- ar/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ar/state_of_js.yml b/ar/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/ar/state_of_js.yml +++ b/ar/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 296e919fc41611e57f710c307096de3871880e66 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:09 +0900 Subject: [PATCH 1139/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 77590c9a2cab3fd825f762910063347e11c94ffd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:10 +0900 Subject: [PATCH 1140/1932] New translations state_of_css.yml (Catalan) --- ca/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ca/state_of_css.yml b/ca/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/ca/state_of_css.yml +++ b/ca/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 55ee9221131dbb872d4b3997105e446e64cd6768 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:11 +0900 Subject: [PATCH 1141/1932] New translations state_of_js.yml (Catalan) --- ca/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ca/state_of_js.yml b/ca/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/ca/state_of_js.yml +++ b/ca/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 10cd2cf5c8f81f3f73b98bd993290790351e7e9b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:12 +0900 Subject: [PATCH 1142/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 29df60138de0fddaf086ad55c639f4f3705e766f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:13 +0900 Subject: [PATCH 1143/1932] New translations state_of_css.yml (Czech) --- cs/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/state_of_css.yml b/cs/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/cs/state_of_css.yml +++ b/cs/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 8d964b0ef81051acda99bb0fcd794d26480ad2dd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:14 +0900 Subject: [PATCH 1144/1932] New translations homepage.yml (English) --- en/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/en/homepage.yml b/en/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/en/homepage.yml +++ b/en/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From c68b64e74c9681b9f519a2f31f6f52dd902a3b66 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:16 +0900 Subject: [PATCH 1145/1932] New translations homepage.yml (French) --- fr/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/fr/homepage.yml b/fr/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/fr/homepage.yml +++ b/fr/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From c3221727d0fae780d3374e6879df89867601838c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:17 +0900 Subject: [PATCH 1146/1932] New translations homepage.yml (Hungarian) --- hu/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/hu/homepage.yml b/hu/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/hu/homepage.yml +++ b/hu/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 6eaeceef410e00346ed1e4c54340b6378f810514 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:17 +0900 Subject: [PATCH 1147/1932] New translations homepage.yml (Spanish) --- es/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/es/homepage.yml b/es/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/es/homepage.yml +++ b/es/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 9646e523d65909448e27913d7704559bcd3e3e66 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:18 +0900 Subject: [PATCH 1148/1932] New translations homepage.yml (Afrikaans) --- af/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/af/homepage.yml b/af/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/af/homepage.yml +++ b/af/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 522815f0ff099a2e9ea4a8144be9f600e280c3a7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:19 +0900 Subject: [PATCH 1149/1932] New translations homepage.yml (Arabic) --- ar/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/ar/homepage.yml b/ar/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/ar/homepage.yml +++ b/ar/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 9dec62158383fbf0b4b10619d69fe23636864dda Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:20 +0900 Subject: [PATCH 1150/1932] New translations homepage.yml (Catalan) --- ca/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/ca/homepage.yml b/ca/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/ca/homepage.yml +++ b/ca/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 3408f177cbf18126594d7a8cbb1cb3ba9875231f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:21 +0900 Subject: [PATCH 1151/1932] New translations homepage.yml (Czech) --- cs/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/cs/homepage.yml b/cs/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/cs/homepage.yml +++ b/cs/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 179395574e94da825a899d9c666048a1ba1183f4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:22 +0900 Subject: [PATCH 1152/1932] New translations homepage.yml (Danish) --- da/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/da/homepage.yml b/da/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/da/homepage.yml +++ b/da/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 04c3f6396b4a90c6bdfb96310e022468b4206ab8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:23 +0900 Subject: [PATCH 1153/1932] New translations homepage.yml (German) --- de/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/de/homepage.yml b/de/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/de/homepage.yml +++ b/de/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From f35f0c815029880a3a9814ca1d36ffcf571bf3a9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:24 +0900 Subject: [PATCH 1154/1932] New translations homepage.yml (Greek) --- el/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/el/homepage.yml b/el/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/el/homepage.yml +++ b/el/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From db5eaad48d2e90dd0a02eec0d39ffb662abd2599 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:25 +0900 Subject: [PATCH 1155/1932] New translations homepage.yml (Finnish) --- fi/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/fi/homepage.yml b/fi/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/fi/homepage.yml +++ b/fi/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 0bde82949301cf034edae96313694f0752ea1fba Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:26 +0900 Subject: [PATCH 1156/1932] New translations homepage.yml (Hebrew) --- he/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/he/homepage.yml b/he/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/he/homepage.yml +++ b/he/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 9b367dd99a30d2df67da04dd7fc031d2b462c012 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:27 +0900 Subject: [PATCH 1157/1932] New translations homepage.yml (Italian) --- it/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/it/homepage.yml b/it/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/it/homepage.yml +++ b/it/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 9ba323bebf0ccd9eb7e686667bc221cc619d06a4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:28 +0900 Subject: [PATCH 1158/1932] New translations homepage.yml (Ukrainian) --- uk/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/uk/homepage.yml b/uk/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/uk/homepage.yml +++ b/uk/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 0847ca0a85d7e89f56d6153ac2b85ae61585867a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:29 +0900 Subject: [PATCH 1159/1932] New translations homepage.yml (Japanese) --- ja/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/ja/homepage.yml b/ja/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/ja/homepage.yml +++ b/ja/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From bc9a4a1a69f344aa7428d850bd3e29ef6b5efe54 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:30 +0900 Subject: [PATCH 1160/1932] New translations homepage.yml (Korean) --- ko/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/ko/homepage.yml b/ko/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/ko/homepage.yml +++ b/ko/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 39961a22772648ad189c39f037f13511f402201f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:31 +0900 Subject: [PATCH 1161/1932] New translations homepage.yml (Dutch) --- nl/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/nl/homepage.yml b/nl/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/nl/homepage.yml +++ b/nl/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From f2d8830373fcd77f73a742407af75985bbdfca7d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:31 +0900 Subject: [PATCH 1162/1932] New translations homepage.yml (Norwegian) --- no/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/no/homepage.yml b/no/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/no/homepage.yml +++ b/no/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 91658f018d3aaa1b8524b3163444f4a0b8c7fe95 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:32 +0900 Subject: [PATCH 1163/1932] New translations homepage.yml (Polish) --- pl/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/pl/homepage.yml b/pl/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/pl/homepage.yml +++ b/pl/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From d3ba3c7404716f263552357d7a1865b6f82b6730 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:34 +0900 Subject: [PATCH 1164/1932] New translations homepage.yml (Russian) --- ru/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/ru/homepage.yml b/ru/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/ru/homepage.yml +++ b/ru/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From f10cd4f9457c1c6810b1e12b8f2bdcde9bbcd62a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:35 +0900 Subject: [PATCH 1165/1932] New translations homepage.yml (Serbian (Cyrillic)) --- sr/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/sr/homepage.yml b/sr/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/sr/homepage.yml +++ b/sr/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 7979c7477f92760db260a7eab867c1fbcc39faed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:36 +0900 Subject: [PATCH 1166/1932] New translations homepage.yml (Swedish) --- sv/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/sv/homepage.yml b/sv/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/sv/homepage.yml +++ b/sv/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 23869f8870e8b0e3992a231e7bbf29d578ed13d2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:37 +0900 Subject: [PATCH 1167/1932] New translations homepage.yml (Turkish) --- tr/homepage.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/tr/homepage.yml b/tr/homepage.yml index 3996a6b5a3f..7b50113cfce 100644 --- a/tr/homepage.yml +++ b/tr/homepage.yml @@ -36,7 +36,7 @@ translations: t: Help Spread the Word! - key: newsletter.stay_tuned - t: Stay Tuned + t: Don't Miss the Next Survey - key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. @@ -46,6 +46,12 @@ translations: - key: homepage.survey_open_now t: Currently Open + - + key: homepage.survey_preview + t: Preview Survey + - + key: homepage.most_recent_survey + t: Most Recent - key: homepage.current_survey t: Current Survey @@ -55,6 +61,9 @@ translations: - key: homepage.view_questions t: View Questions + - + key: homepage.preview_questions + t: Preview Questions - #newsletter key: homepage.newsletter.email From 07e04065655a9555308ab7ce53b8de80b0b220f7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:38 +0900 Subject: [PATCH 1168/1932] New translations state_of_js.yml (Czech) --- cs/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/state_of_js.yml b/cs/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/cs/state_of_js.yml +++ b/cs/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 18c4a527638b24d1b6c8606c95329438da294560 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:39 +0900 Subject: [PATCH 1169/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From b1920586b3755f28509accada9776d03a322b5b2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:40 +0900 Subject: [PATCH 1170/1932] New translations state_of_css.yml (Portuguese) --- pt/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pt/state_of_css.yml b/pt/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/pt/state_of_css.yml +++ b/pt/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 54f31045d6e16ce8479dead6102be1d785632b2c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:41 +0900 Subject: [PATCH 1171/1932] New translations state_of_css.yml (Dutch) --- nl/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nl/state_of_css.yml b/nl/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/nl/state_of_css.yml +++ b/nl/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From f307e9384990636133234d70060e9fa41d9b2c93 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:42 +0900 Subject: [PATCH 1172/1932] New translations state_of_js.yml (Dutch) --- nl/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nl/state_of_js.yml b/nl/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/nl/state_of_js.yml +++ b/nl/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 95e3feb29e17aa13d23a776c69dc04d2d8c4b2a5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:43 +0900 Subject: [PATCH 1173/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 9d583be5615f1b02d492a07e94ca2ec080a85a54 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:44 +0900 Subject: [PATCH 1174/1932] New translations state_of_css.yml (Norwegian) --- no/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/no/state_of_css.yml b/no/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/no/state_of_css.yml +++ b/no/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From b16a3e11ec8853b572adc888242540bf09607f63 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:46 +0900 Subject: [PATCH 1175/1932] New translations state_of_js.yml (Norwegian) --- no/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/no/state_of_js.yml b/no/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/no/state_of_js.yml +++ b/no/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From e74f882d1a9fc5e3fe202ace16ea6b651800a6d1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:47 +0900 Subject: [PATCH 1176/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 6c5e7f7ccb50b2912eab2f5b710fc9edfcd52bc9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:48 +0900 Subject: [PATCH 1177/1932] New translations state_of_css.yml (Polish) --- pl/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pl/state_of_css.yml b/pl/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/pl/state_of_css.yml +++ b/pl/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From afd867d3d4450e4a9a4eae2bec5833c8d23375b4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:49 +0900 Subject: [PATCH 1178/1932] New translations state_of_js.yml (Polish) --- pl/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pl/state_of_js.yml b/pl/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/pl/state_of_js.yml +++ b/pl/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 0fc5b185035744014d328c8960c4a82c3a6fbbe4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:50 +0900 Subject: [PATCH 1179/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From f226444f9978fc8590d553cbbf94a4f9cd921401 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:51 +0900 Subject: [PATCH 1180/1932] New translations state_of_js.yml (Portuguese) --- pt/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pt/state_of_js.yml b/pt/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/pt/state_of_js.yml +++ b/pt/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 3da47bdf2a7fa16ce35bce8979f4dc2d64d40d88 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:51 +0900 Subject: [PATCH 1181/1932] New translations state_of_js.yml (Korean) --- ko/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/state_of_js.yml b/ko/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/ko/state_of_js.yml +++ b/ko/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 7e591529258a6dfca3363641b5224b54d7ef88ab Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:52 +0900 Subject: [PATCH 1182/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 8959a67a5ba005b97b0519ea9e45cdaa198522c4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:54 +0900 Subject: [PATCH 1183/1932] New translations state_of_css.yml (Russian) --- ru/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru/state_of_css.yml b/ru/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/ru/state_of_css.yml +++ b/ru/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 7a419d541d4b7edc0c8d3a04308aa02ffa78f0ba Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:55 +0900 Subject: [PATCH 1184/1932] New translations state_of_js.yml (Russian) --- ru/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru/state_of_js.yml b/ru/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/ru/state_of_js.yml +++ b/ru/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 01e7ba4f9323ec1a5cea3a0e80b61d4669968f39 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:56 +0900 Subject: [PATCH 1185/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 8f50a4e7b243cc8af69fab1410078ec43ee19cf0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:57 +0900 Subject: [PATCH 1186/1932] New translations state_of_css.yml (Serbian (Cyrillic)) --- sr/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sr/state_of_css.yml b/sr/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/sr/state_of_css.yml +++ b/sr/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 0466c224f6afc24596012d63ce07cf19dea5c5f8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:58 +0900 Subject: [PATCH 1187/1932] New translations state_of_js.yml (Serbian (Cyrillic)) --- sr/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sr/state_of_js.yml b/sr/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/sr/state_of_js.yml +++ b/sr/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 28176d10094435967adef23e49b662051391076b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:31:59 +0900 Subject: [PATCH 1188/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 50006642d1621a895044c92df721525b26c62bc0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:02 +0900 Subject: [PATCH 1189/1932] New translations state_of_css.yml (Swedish) --- sv/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv/state_of_css.yml b/sv/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/sv/state_of_css.yml +++ b/sv/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 51e1867bad4903727381fc8949d3c31de67e2f25 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:03 +0900 Subject: [PATCH 1190/1932] New translations state_of_js.yml (Swedish) --- sv/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv/state_of_js.yml b/sv/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/sv/state_of_js.yml +++ b/sv/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 87e6f12e2f595d2d3e78fb5d00795333201a40f2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:04 +0900 Subject: [PATCH 1191/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 95da78b14f4906dabc78f7921c8f4da0441c65f2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:05 +0900 Subject: [PATCH 1192/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 82356ba244748c12717eaaf6d5f9ead634327574 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:06 +0900 Subject: [PATCH 1193/1932] New translations state_of_css.yml (Korean) --- ko/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/state_of_css.yml b/ko/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/ko/state_of_css.yml +++ b/ko/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 7b52b5e0e3fe61e051fe8fccc503f8469abdd483 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:07 +0900 Subject: [PATCH 1194/1932] New translations state_of_css.yml (Danish) --- da/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/da/state_of_css.yml b/da/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/da/state_of_css.yml +++ b/da/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 319e9f1be1a688d3206db579b60ca4f93ad63220 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:08 +0900 Subject: [PATCH 1195/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From e7faa1d3d33d4f3b6cf31b9e50126c52d92cf3c4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:09 +0900 Subject: [PATCH 1196/1932] New translations state_of_js.yml (Danish) --- da/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/da/state_of_js.yml b/da/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/da/state_of_js.yml +++ b/da/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From ee650eb7634d0066c889d92284cd1a3018ebe494 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:10 +0900 Subject: [PATCH 1197/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From c8ce61405367b93c46d46c00e5217b3d85bec199 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:11 +0900 Subject: [PATCH 1198/1932] New translations state_of_css.yml (German) --- de/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/de/state_of_css.yml b/de/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/de/state_of_css.yml +++ b/de/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 1e06e70994b566f0656e41455b1114386990f691 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:12 +0900 Subject: [PATCH 1199/1932] New translations state_of_js.yml (German) --- de/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/de/state_of_js.yml b/de/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/de/state_of_js.yml +++ b/de/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 42bf17ab91ba1df054a8118b0662dfe8d41f80a9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:13 +0900 Subject: [PATCH 1200/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 1258ad1c70b1feb5a2c574433a3cb216310aec5d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:14 +0900 Subject: [PATCH 1201/1932] New translations state_of_css.yml (Greek) --- el/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/el/state_of_css.yml b/el/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/el/state_of_css.yml +++ b/el/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 9668976ed6b4b00aef0a0bf40680110ba03aa44f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:15 +0900 Subject: [PATCH 1202/1932] New translations state_of_js.yml (Greek) --- el/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/el/state_of_js.yml b/el/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/el/state_of_js.yml +++ b/el/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 3d81e10c5c2f0c6ba1d9104ca3925dc8a53285a2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:16 +0900 Subject: [PATCH 1203/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 85b435ec66758138fa465b0bc34fd0ed7c129e46 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:17 +0900 Subject: [PATCH 1204/1932] New translations state_of_css.yml (Finnish) --- fi/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi/state_of_css.yml b/fi/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/fi/state_of_css.yml +++ b/fi/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 10adb608f00afd9177e936f51b984570a7b7d8bc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:18 +0900 Subject: [PATCH 1205/1932] New translations state_of_js.yml (Finnish) --- fi/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi/state_of_js.yml b/fi/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/fi/state_of_js.yml +++ b/fi/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From c669f8e34529fea447aebf89220cfdafff08af08 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:19 +0900 Subject: [PATCH 1206/1932] New translations state_of_css.yml (Hebrew) --- he/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/he/state_of_css.yml b/he/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/he/state_of_css.yml +++ b/he/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 5a35986ba06b2e666528146f0f3c4b82139fb3aa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:20 +0900 Subject: [PATCH 1207/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 285c5da47f6d3f51193864e26b57d0b69ee011f4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:21 +0900 Subject: [PATCH 1208/1932] New translations state_of_js.yml (Hebrew) --- he/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/he/state_of_js.yml b/he/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/he/state_of_js.yml +++ b/he/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From c1d9381b2b63c28cb6f171d6c3f252488f78d03e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:22 +0900 Subject: [PATCH 1209/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From dd0fbc27e6c15d92a896073ef94064af5228c161 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:23 +0900 Subject: [PATCH 1210/1932] New translations state_of_css.yml (Hungarian) --- hu/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hu/state_of_css.yml b/hu/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/hu/state_of_css.yml +++ b/hu/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From db059efc9b850a5b8cda8ad0af35e1a60a394e42 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:24 +0900 Subject: [PATCH 1211/1932] New translations state_of_js.yml (Hungarian) --- hu/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hu/state_of_js.yml b/hu/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/hu/state_of_js.yml +++ b/hu/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From a621fb84654651bcf9cd9ce4970a1f32d877aa9b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:25 +0900 Subject: [PATCH 1212/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 3191d360a9f3a982fe00e1f576e25fc0ccdabb32 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:26 +0900 Subject: [PATCH 1213/1932] New translations state_of_css.yml (Italian) --- it/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/it/state_of_css.yml b/it/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/it/state_of_css.yml +++ b/it/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 4a9b891e17caefc241f832a383fcdee665bc5b67 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:27 +0900 Subject: [PATCH 1214/1932] New translations state_of_js.yml (Italian) --- it/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/it/state_of_js.yml b/it/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/it/state_of_js.yml +++ b/it/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 4747634b7ab7d9f1e29cc7bf928f41647a23174c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:28 +0900 Subject: [PATCH 1215/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From daf144bdc90d2ac56d5559454db5bad3ded5160c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:30 +0900 Subject: [PATCH 1216/1932] New translations state_of_css.yml (Japanese) --- ja/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/state_of_css.yml b/ja/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/ja/state_of_css.yml +++ b/ja/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From a798fe2086b51e957ccfdf6006a2e3f90253ebc8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:31 +0900 Subject: [PATCH 1217/1932] New translations state_of_js.yml (Japanese) --- ja/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/state_of_js.yml b/ja/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/ja/state_of_js.yml +++ b/ja/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From f91580647b9457f5b1298f13ad1def665ef78dae Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:31 +0900 Subject: [PATCH 1218/1932] New translations state_of_css.yml (Turkish) --- tr/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/state_of_css.yml b/tr/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/tr/state_of_css.yml +++ b/tr/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 4025063c967425bbef06355614cbcf9077a88bbe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:32 +0900 Subject: [PATCH 1219/1932] New translations state_of_js.yml (Turkish) --- tr/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/state_of_js.yml b/tr/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/tr/state_of_js.yml +++ b/tr/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 2d17f8f673de190f12b37f7293280e0ff7ceaa54 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:34 +0900 Subject: [PATCH 1220/1932] New translations state_of_css.yml (English) --- en/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/state_of_css.yml b/en/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/en/state_of_css.yml +++ b/en/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 9039193223764a0cdf9e216f490327ea75238419 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:36 +0900 Subject: [PATCH 1221/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 40dca5405cca755f20a5c32a43a6e481504808d5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:37 +0900 Subject: [PATCH 1222/1932] New translations state_of_js.yml (Vietnamese) --- vi/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vi/state_of_js.yml b/vi/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/vi/state_of_js.yml +++ b/vi/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 9fb5cf72023a77f52637115c35914ac64ebe9332 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:38 +0900 Subject: [PATCH 1223/1932] New translations state_of_css.yml (Vietnamese) --- vi/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vi/state_of_css.yml b/vi/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/vi/state_of_css.yml +++ b/vi/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From bbb6e0475f04fa790a81a2de86ef39efc26b7ea2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:39 +0900 Subject: [PATCH 1224/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From acbbd552b171384a1e32ff25be84f3bdd1d1df02 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:40 +0900 Subject: [PATCH 1225/1932] New translations state_of_js.yml (English) --- en/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/state_of_js.yml b/en/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/en/state_of_js.yml +++ b/en/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 50acaa0de87e4eb7ef932c84957415c618cf1cd6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:41 +0900 Subject: [PATCH 1226/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 47ffcf89e28ff1d77e9e4fe38ed854fce5bce5b5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:42 +0900 Subject: [PATCH 1227/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 210a29b3165bba77d83031775e4f57cae7ecedf1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:43 +0900 Subject: [PATCH 1228/1932] New translations state_of_js.yml (Chinese Traditional) --- zh/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/state_of_js.yml b/zh/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/zh/state_of_js.yml +++ b/zh/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From e783fe2fec0434cb28d009db600bfd0ee8ea03b0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:44 +0900 Subject: [PATCH 1229/1932] New translations state_of_css.yml (Chinese Traditional) --- zh/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/state_of_css.yml b/zh/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/zh/state_of_css.yml +++ b/zh/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 87675a46e6d5fb6e8e35de54ce3563cf780cecf7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:47 +0900 Subject: [PATCH 1230/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index 7389f3cd337..cd5f0d9882a 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -15,7 +15,7 @@ translations: Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! - key: general.state_of_graphql.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the GraphQL ecosystem - ########################################################################### #Survey From 2c83b3fe5613308231c878226980372c7e1df74f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:48 +0900 Subject: [PATCH 1231/1932] New translations state_of_js.yml (Ukrainian) --- uk/state_of_js.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/state_of_js.yml b/uk/state_of_js.yml index 7649956d928..f11bed31b95 100644 --- a/uk/state_of_js.yml +++ b/uk/state_of_js.yml @@ -15,7 +15,7 @@ translations: Together, let's find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more. - key: general.state_of_js.description - t: The annual survey of the JavaScript ecosystem. + t: The annual developer survey of the JavaScript ecosystem - ########################################################################### #Sections From 1951971f40da0caf3c8ce4b78f245734c923446e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sat, 11 Jun 2022 08:32:49 +0900 Subject: [PATCH 1232/1932] New translations state_of_css.yml (Ukrainian) --- uk/state_of_css.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/state_of_css.yml b/uk/state_of_css.yml index 2ef5c3308e5..5b1690df2d9 100644 --- a/uk/state_of_css.yml +++ b/uk/state_of_css.yml @@ -15,7 +15,7 @@ translations: So after the success of our annual State Of JavaScript survey, we’ve decided to take on the world of styles and selectors. We're hoping you’ll help us identify the latest trends, and figure out what tools to learn and use next! - key: general.state_of_css.description - t: The annual survey about the latest trends in CSS. + t: The annual developer survey about the latest trends in CSS - ########################################################################### #Sections From 0e6fa8c25a40ae052cad2d56eba4809658e0e160 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:49 +0900 Subject: [PATCH 1233/1932] New translations common.yml (Romanian) --- ro/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ro/common.yml b/ro/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 3c71c1a1308c6e4ed97f56607894e805d6a6f228 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:50 +0900 Subject: [PATCH 1234/1932] New translations homepage.yml (Danish) --- da/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/da/homepage.yml b/da/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/da/homepage.yml +++ b/da/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 57ce24ff932d8aa7e6baa99991962c50e1b26188 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:51 +0900 Subject: [PATCH 1235/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/vi/common.yml b/vi/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 334c195e8cdaf4738d61047d11caa946f3bee90c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:52 +0900 Subject: [PATCH 1236/1932] New translations common.yml (Portuguese, Brazilian) --- pt/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pt/common.yml b/pt/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From a3122e31d6201ad4413dfde1991c7b956eefb08d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:53 +0900 Subject: [PATCH 1237/1932] New translations homepage.yml (Romanian) --- ro/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ro/homepage.yml b/ro/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/ro/homepage.yml +++ b/ro/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 872eceddd9fb0c90ad25253bb2e52ad5f73ff8e1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:54 +0900 Subject: [PATCH 1238/1932] New translations homepage.yml (French) --- fr/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/homepage.yml b/fr/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/fr/homepage.yml +++ b/fr/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 8bca76dce7567b9a297ede42fd12dd677eab5838 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:55 +0900 Subject: [PATCH 1239/1932] New translations homepage.yml (Spanish) --- es/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es/homepage.yml b/es/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/es/homepage.yml +++ b/es/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From cafcbf6ab4176fd60981600353428749e9884215 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:56 +0900 Subject: [PATCH 1240/1932] New translations homepage.yml (Afrikaans) --- af/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/af/homepage.yml b/af/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/af/homepage.yml +++ b/af/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 6fff9e81eb83d0dbbd90cab9ac4d167a0b19a11b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:57 +0900 Subject: [PATCH 1241/1932] New translations homepage.yml (Arabic) --- ar/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ar/homepage.yml b/ar/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/ar/homepage.yml +++ b/ar/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 4209019127fc39559773245c1b23d99c5ea48006 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:57 +0900 Subject: [PATCH 1242/1932] New translations homepage.yml (Catalan) --- ca/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ca/homepage.yml b/ca/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/ca/homepage.yml +++ b/ca/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 9b723e19d512f3ae470e88ff0f602931fe1c1db0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:58 +0900 Subject: [PATCH 1243/1932] New translations homepage.yml (Czech) --- cs/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/homepage.yml b/cs/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/cs/homepage.yml +++ b/cs/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 61d68df7be07a9774909acd436a0992602ac97bf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:42:59 +0900 Subject: [PATCH 1244/1932] New translations homepage.yml (German) --- de/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/de/homepage.yml b/de/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/de/homepage.yml +++ b/de/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 883b2562ba3acc2fc821f260f7877ba57799375c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:00 +0900 Subject: [PATCH 1245/1932] New translations common.yml (Chinese Traditional) --- zh/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/zh/common.yml b/zh/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 0f66994548799029d316c9ea63d364966a675e17 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:01 +0900 Subject: [PATCH 1246/1932] New translations homepage.yml (Greek) --- el/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/el/homepage.yml b/el/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/el/homepage.yml +++ b/el/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 0026679e5524d109bd1ba7fead23cc6d445f414b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:02 +0900 Subject: [PATCH 1247/1932] New translations homepage.yml (Finnish) --- fi/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi/homepage.yml b/fi/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/fi/homepage.yml +++ b/fi/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 4928d5309fce359a9c8c10debce6762ffcdfb282 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:03 +0900 Subject: [PATCH 1248/1932] New translations homepage.yml (Hebrew) --- he/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/he/homepage.yml b/he/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/he/homepage.yml +++ b/he/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From af9a893ef49c438d2cd653411c62d3215c066802 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:04 +0900 Subject: [PATCH 1249/1932] New translations homepage.yml (Hungarian) --- hu/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hu/homepage.yml b/hu/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/hu/homepage.yml +++ b/hu/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 72b0ac1418c436bc08289d35718aca8fd521964c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:05 +0900 Subject: [PATCH 1250/1932] New translations homepage.yml (Italian) --- it/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/it/homepage.yml b/it/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/it/homepage.yml +++ b/it/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From ffdfbc7eb91b29ec461e543c9b13fdb0fdbea8de Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:06 +0900 Subject: [PATCH 1251/1932] New translations homepage.yml (Japanese) --- ja/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/homepage.yml b/ja/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/ja/homepage.yml +++ b/ja/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From c996109d693cfed7ba0d1e6278a2e87a0dea8419 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:07 +0900 Subject: [PATCH 1252/1932] New translations homepage.yml (Korean) --- ko/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/homepage.yml b/ko/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/ko/homepage.yml +++ b/ko/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From be9e4d1a3f98c14319475d3fce75f75b8f64d191 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:08 +0900 Subject: [PATCH 1253/1932] New translations homepage.yml (Dutch) --- nl/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nl/homepage.yml b/nl/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/nl/homepage.yml +++ b/nl/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 535a89a15a1346f031072e3d9216137ed1168ee4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:09 +0900 Subject: [PATCH 1254/1932] New translations homepage.yml (Norwegian) --- no/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/no/homepage.yml b/no/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/no/homepage.yml +++ b/no/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 2476e6f600fcaa9ae5332ee3c3a793893b8796f6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:10 +0900 Subject: [PATCH 1255/1932] New translations homepage.yml (Polish) --- pl/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pl/homepage.yml b/pl/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/pl/homepage.yml +++ b/pl/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From e83e746182afde84ffe09010ced64c8d24fe0f24 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:11 +0900 Subject: [PATCH 1256/1932] New translations common.yml (English) --- en/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/en/common.yml b/en/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/en/common.yml +++ b/en/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 97ab2c26f351802008936ae3a1cbe3026300d746 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:13 +0900 Subject: [PATCH 1257/1932] New translations common.yml (French) --- fr/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fr/common.yml b/fr/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 84c745970356034df13b8dcb11dc9d49f4798c75 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:14 +0900 Subject: [PATCH 1258/1932] New translations common.yml (Hungarian) --- hu/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/hu/common.yml b/hu/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 3ad93d9f7c957ec460cf160a650a0853e33adee1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:17 +0900 Subject: [PATCH 1259/1932] New translations common.yml (Spanish) --- es/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/es/common.yml b/es/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/es/common.yml +++ b/es/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 6fe1b6d5f8c816b44c796fd46b8fc7d220df7860 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:20 +0900 Subject: [PATCH 1260/1932] New translations common.yml (Afrikaans) --- af/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/af/common.yml b/af/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/af/common.yml +++ b/af/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 5aae1f9dbc6f05d2708888ab503760f3f86f76ef Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:22 +0900 Subject: [PATCH 1261/1932] New translations common.yml (Arabic) --- ar/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ar/common.yml b/ar/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 9034eaa17c8a32504b14ed36491be345ddf57e13 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:23 +0900 Subject: [PATCH 1262/1932] New translations common.yml (Catalan) --- ca/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ca/common.yml b/ca/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 839fb6bbb7297d74e459e773c4d80549b485dc5a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:24 +0900 Subject: [PATCH 1263/1932] New translations common.yml (Czech) --- cs/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/cs/common.yml b/cs/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 8e5ceb37d0f0b9a0029db3556f4659437a61e104 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:25 +0900 Subject: [PATCH 1264/1932] New translations common.yml (Danish) --- da/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/da/common.yml b/da/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/da/common.yml +++ b/da/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From ed03b26fa27f5017492936b1bd2839b53e26e8f5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:26 +0900 Subject: [PATCH 1265/1932] New translations common.yml (German) --- de/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/de/common.yml b/de/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/de/common.yml +++ b/de/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 5b7eb84ce114fb418d16b18e049aafd546202b5b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:27 +0900 Subject: [PATCH 1266/1932] New translations common.yml (Greek) --- el/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/el/common.yml b/el/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/el/common.yml +++ b/el/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 7943586cad814cd96b791972a0e7817f74ce40d6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:30 +0900 Subject: [PATCH 1267/1932] New translations common.yml (Finnish) --- fi/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fi/common.yml b/fi/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 5d37012c2cb69b6f866807d6d534f4e4d1d5289e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:32 +0900 Subject: [PATCH 1268/1932] New translations common.yml (Hebrew) --- he/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/he/common.yml b/he/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/he/common.yml +++ b/he/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 4ec2ffec698857f5c9c51c46bde019a19563771b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:33 +0900 Subject: [PATCH 1269/1932] New translations common.yml (Italian) --- it/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/it/common.yml b/it/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/it/common.yml +++ b/it/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 98b7b359dd1ede4556a8d8cd641b9eceb4eb04f5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:34 +0900 Subject: [PATCH 1270/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/uk/common.yml b/uk/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 10ab118c322c5abe592700de38af463fc1372062 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:35 +0900 Subject: [PATCH 1271/1932] New translations common.yml (Japanese) --- ja/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ja/common.yml b/ja/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 37c81a07f53725017729d95f3c2b14d7f67230a6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:36 +0900 Subject: [PATCH 1272/1932] New translations common.yml (Korean) --- ko/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ko/common.yml b/ko/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From e9f22a223452ef945130ec85436a0cecb80eb566 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:37 +0900 Subject: [PATCH 1273/1932] New translations common.yml (Dutch) --- nl/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/nl/common.yml b/nl/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From e4e87e689afd3d992fef83c1af7553f32e67a5ae Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:38 +0900 Subject: [PATCH 1274/1932] New translations common.yml (Norwegian) --- no/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/no/common.yml b/no/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/no/common.yml +++ b/no/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From cb5ffd208bed2b6eaf79eefa16c37abdbf570585 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:39 +0900 Subject: [PATCH 1275/1932] New translations common.yml (Polish) --- pl/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pl/common.yml b/pl/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 2aa707a47f91a5d786cbb49626211b4939c2e794 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:41 +0900 Subject: [PATCH 1276/1932] New translations common.yml (Russian) --- ru/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ru/common.yml b/ru/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From c50c945bfb432f8911cc147221d88d0d0facbdaf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:42 +0900 Subject: [PATCH 1277/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sr/common.yml b/sr/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 5b3e96576e21926622ad177a8bfd70cdac55b511 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:43 +0900 Subject: [PATCH 1278/1932] New translations common.yml (Swedish) --- sv/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sv/common.yml b/sv/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From 01a9623f3e478c85398c69b5675269a8b6a9381c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:45 +0900 Subject: [PATCH 1279/1932] New translations common.yml (Turkish) --- tr/common.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tr/common.yml b/tr/common.yml index 894c5fe6237..00abe03cf58 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -99,6 +99,9 @@ translations: - key: general.new t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. - #credits key: credits.thanks From c18955385a757c3b3a03120e446bc0752aae388b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:46 +0900 Subject: [PATCH 1280/1932] New translations homepage.yml (Portuguese) --- pt/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pt/homepage.yml b/pt/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/pt/homepage.yml +++ b/pt/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From f7a1e41be6d1ebf909d78d54d22c63814bf7fb23 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:47 +0900 Subject: [PATCH 1281/1932] New translations homepage.yml (Russian) --- ru/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru/homepage.yml b/ru/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/ru/homepage.yml +++ b/ru/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 1b2b56294515192ff41ea4ae43e52d8f351d1bed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:48 +0900 Subject: [PATCH 1282/1932] New translations homepage.yml (Serbian (Cyrillic)) --- sr/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sr/homepage.yml b/sr/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/sr/homepage.yml +++ b/sr/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 658dde1196978a8bbdf1342e70bb0ba81a69a106 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:49 +0900 Subject: [PATCH 1283/1932] New translations homepage.yml (Swedish) --- sv/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv/homepage.yml b/sv/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/sv/homepage.yml +++ b/sv/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 0fa6287f27fc46a9ddfcc73794570525626611a1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:50 +0900 Subject: [PATCH 1284/1932] New translations homepage.yml (Turkish) --- tr/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/homepage.yml b/tr/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/tr/homepage.yml +++ b/tr/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From b2bbb553cbca9151bd81ff240a43ebbdde3a5f65 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:51 +0900 Subject: [PATCH 1285/1932] New translations homepage.yml (Ukrainian) --- uk/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/homepage.yml b/uk/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/uk/homepage.yml +++ b/uk/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 341990640fed837e90a9434fde5594c59f58017e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:51 +0900 Subject: [PATCH 1286/1932] New translations homepage.yml (Chinese Simplified) --- zh/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/homepage.yml b/zh/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/zh/homepage.yml +++ b/zh/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 26d7a47c5b0a8144bc2778ae2a85b043e6b69fcc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:53 +0900 Subject: [PATCH 1287/1932] New translations homepage.yml (English) --- en/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/homepage.yml b/en/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/en/homepage.yml +++ b/en/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From 7630858b9012ca78880c0292b5a622e9a62971c5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 10:43:54 +0900 Subject: [PATCH 1288/1932] New translations homepage.yml (Vietnamese) --- vi/homepage.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vi/homepage.yml b/vi/homepage.yml index 7b50113cfce..0493774c86b 100644 --- a/vi/homepage.yml +++ b/vi/homepage.yml @@ -77,4 +77,4 @@ translations: t: 'Available languages:' - key: languages.help_us_translate - t: Help us translate the survey in your language. + t: Help us translate the survey in your language → From c845211fc4a2fd4732dc8532ab923fba20f63c92 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:45 +0900 Subject: [PATCH 1289/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From cc7bd4a3792e33e1ead969b8d16231d52427ff6b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:47 +0900 Subject: [PATCH 1290/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 72d896f2ddbc346d5c994d34bf8662eac7e0f57a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:48 +0900 Subject: [PATCH 1291/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 73e93d8b99672f99d4838dcece62118d4f697b3d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:49 +0900 Subject: [PATCH 1292/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 46140fb42cb11c62f947b00de80de706a313859e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:50 +0900 Subject: [PATCH 1293/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 83eec8efe8d1ce62f45d26d982bd9e05ee78c673 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:51 +0900 Subject: [PATCH 1294/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 517bf241d09526b27902fe42f8a857021e85c275 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:52 +0900 Subject: [PATCH 1295/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 975fa06bac2449352c16ecd8bbb2d5c9afb966e1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:53 +0900 Subject: [PATCH 1296/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From daf40eb22b2438fef67c58666d9936d4e4c7b91c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:55 +0900 Subject: [PATCH 1297/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 658ba39664716639964c1e5d96f76b021470c56a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:56 +0900 Subject: [PATCH 1298/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From ed93518e8242222e28738639ed9e7a55dca36ed7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:57 +0900 Subject: [PATCH 1299/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From a1dca7c148f9889fa01c28cde33e2e77bc37357f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:58 +0900 Subject: [PATCH 1300/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 346405c42f87a22ce33912ff4ae88a25670c32be Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:44:59 +0900 Subject: [PATCH 1301/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 9721ffe075febb2b546b6a8e5aa1f63b4adc1b7b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:00 +0900 Subject: [PATCH 1302/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 02955a9bad8007c9ab15760175ed60a7d67e96e4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:01 +0900 Subject: [PATCH 1303/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From d621b222165c95799d76b690fcb980992bba199b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:02 +0900 Subject: [PATCH 1304/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 3424831b66a104198a459aa1978c21ac292e081b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:04 +0900 Subject: [PATCH 1305/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From e30910881bffdc9f996ce126da77cf80dd1e7cef Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:05 +0900 Subject: [PATCH 1306/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From e95a45644c1d7694c563dc1b7cbd71535457fba7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:06 +0900 Subject: [PATCH 1307/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 3d56495c469cd93992dc7926e6d6fc575d58a5d5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:07 +0900 Subject: [PATCH 1308/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From cc645b7eb4ea3b8b89a7d90ea52f54d1422d597f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:08 +0900 Subject: [PATCH 1309/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From bc3ffbce61cc7bfd17fc27d3ef15ec0d2634c13b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:09 +0900 Subject: [PATCH 1310/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 291d3bb5cabed551218b7e6141979cb466bfe0ac Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:10 +0900 Subject: [PATCH 1311/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 02cee3669d58bbecadadec55c8d76477927e9ab9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:11 +0900 Subject: [PATCH 1312/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 913a8efb2ee935bdf0f6d6fdac8c36ab5ea20fa3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:12 +0900 Subject: [PATCH 1313/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 1c9b9008213b05857123b24212a20cb7b4af551a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:13 +0900 Subject: [PATCH 1314/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 4d1fd797aefb2a3cb3b871138bfe4e5bc75e5203 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:14 +0900 Subject: [PATCH 1315/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From 068399e41845c8cb10af675a49b7123b307f1e40 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 14 Jun 2022 11:45:15 +0900 Subject: [PATCH 1316/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index cd5f0d9882a..2a96d8af9d4 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -20,11 +20,11 @@ translations: ########################################################################### #Survey ########################################################################### - key: features.features_intro + key: features.graphql_features_intro t: > Welcome to the survey! This first part is all about figuring out which **features** of GraphQL and its ecosystem you know about. And if you know about something but haven't yet used it, that's fine too! - - key: tools.tools_intro + key: tools.graphql_tools_intro t: > The next couple sections focus on the **libraries** and **services** that make up the GraphQL ecosystem. Let us know what you're excited about! - From f04033d375d89c0b0aeadf66f4f5e02db8b31e75 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:26 +0900 Subject: [PATCH 1317/1932] New translations homepage.yml (Romanian) --- ro/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/ro/homepage.yml b/ro/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/ro/homepage.yml +++ b/ro/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From ca057ea55750e317bae5462ba0436beff59ac2bc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:27 +0900 Subject: [PATCH 1318/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From eb34350214f0cf954b11bae5188d15c9c2821c70 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:28 +0900 Subject: [PATCH 1319/1932] New translations homepage.yml (Vietnamese) --- vi/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/vi/homepage.yml b/vi/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/vi/homepage.yml +++ b/vi/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 49384ab8da4899452e335cfd0d8d7216844dcabe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:30 +0900 Subject: [PATCH 1320/1932] New translations homepage.yml (Portuguese, Brazilian) --- pt/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/pt/homepage.yml b/pt/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/pt/homepage.yml +++ b/pt/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From a5b66878d80f6f1e6a90619da3aa98bad3cf2da8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:31 +0900 Subject: [PATCH 1321/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 024128b2a63cf99e33959c8abe21ad0794695d09 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:32 +0900 Subject: [PATCH 1322/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From acc787a8c88dad77029cb08781045133d7252586 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:33 +0900 Subject: [PATCH 1323/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From f1614a70c2c9248ffaf42b192e1b00eaf42e318a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:34 +0900 Subject: [PATCH 1324/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From aade3d6e8620f9d9b944551a5745ded06fcf5c8d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:35 +0900 Subject: [PATCH 1325/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From ce18f3f3f973804bb55449278548a76fc5cd006f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:36 +0900 Subject: [PATCH 1326/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From aa4fa9a8dc194849a9c2e51ceecd3766ce6d1e81 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:37 +0900 Subject: [PATCH 1327/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From ce49656d53a616bfcc912c55fd17dd692eadd92b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:38 +0900 Subject: [PATCH 1328/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 6e011e42bfda6553003da7ddc4321d002f20e295 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:39 +0900 Subject: [PATCH 1329/1932] New translations homepage.yml (Chinese Traditional) --- zh/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/zh/homepage.yml b/zh/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/zh/homepage.yml +++ b/zh/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 04258d9521c0d31c97e3a7cff9d4efae5e340682 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:40 +0900 Subject: [PATCH 1330/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From cf2252b698733b2ec47790acd5cdb6bc3c942f37 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:41 +0900 Subject: [PATCH 1331/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 37d8fedf396f577a0900f1ddb525df4498cad2b3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:42 +0900 Subject: [PATCH 1332/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 7de78e5d9c90d6477893962f925c67421bfcab27 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:44 +0900 Subject: [PATCH 1333/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From caf10aa822a0791861fda32cdd2f6c9cc1058742 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:45 +0900 Subject: [PATCH 1334/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 3f1474b0ee6c778ecf1ea8979b093097af00bc3b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:46 +0900 Subject: [PATCH 1335/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From b681526f911f373544bbd7ecfe4e0c2f425603cf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:47 +0900 Subject: [PATCH 1336/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 4d8b7b5e0437ce0ee3a63da62b2cd93e7cba3dd4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:48 +0900 Subject: [PATCH 1337/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 1abbeda75e10b1adb988e7d2dd5cffa84616d066 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:49 +0900 Subject: [PATCH 1338/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From a25c0f0886c9d0da02457531bd2c017472006cd0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:50 +0900 Subject: [PATCH 1339/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 852e8ff56577c6341516b771945970ec0ffbb763 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:51 +0900 Subject: [PATCH 1340/1932] New translations homepage.yml (English) --- en/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/en/homepage.yml b/en/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/en/homepage.yml +++ b/en/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 081dc1803db90dc806da05cefc82dd8f1a5babb2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:53 +0900 Subject: [PATCH 1341/1932] New translations homepage.yml (French) --- fr/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/fr/homepage.yml b/fr/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/fr/homepage.yml +++ b/fr/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 39ef990eecda5b942436a6ecc290b315036b412f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:54 +0900 Subject: [PATCH 1342/1932] New translations homepage.yml (Hungarian) --- hu/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/hu/homepage.yml b/hu/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/hu/homepage.yml +++ b/hu/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 725681a447452ac9da24c5ff76d1b0399a8b153b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:55 +0900 Subject: [PATCH 1343/1932] New translations homepage.yml (Spanish) --- es/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/es/homepage.yml b/es/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/es/homepage.yml +++ b/es/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 3dc1921386671e01dbe26aa2049656f32da3d71b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:56 +0900 Subject: [PATCH 1344/1932] New translations homepage.yml (Afrikaans) --- af/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/af/homepage.yml b/af/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/af/homepage.yml +++ b/af/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 54533b05455f9ebf439afbde0fa478ff80c68158 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:57 +0900 Subject: [PATCH 1345/1932] New translations homepage.yml (Arabic) --- ar/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/ar/homepage.yml b/ar/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/ar/homepage.yml +++ b/ar/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From a9501c0334ed707ee831132328c00f021d63e7a3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:58 +0900 Subject: [PATCH 1346/1932] New translations homepage.yml (Catalan) --- ca/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/ca/homepage.yml b/ca/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/ca/homepage.yml +++ b/ca/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 53228493c125632dbd7dc17ed8efd4b9ad17cabe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:59 +0900 Subject: [PATCH 1347/1932] New translations homepage.yml (Czech) --- cs/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/cs/homepage.yml b/cs/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/cs/homepage.yml +++ b/cs/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 5f18e09f236309b6bd1872a7eaf0f6c70fed49d8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:22:59 +0900 Subject: [PATCH 1348/1932] New translations homepage.yml (Danish) --- da/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/da/homepage.yml b/da/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/da/homepage.yml +++ b/da/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From f2863f93e31d16ab3b789588341b12650888709b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:01 +0900 Subject: [PATCH 1349/1932] New translations homepage.yml (German) --- de/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/de/homepage.yml b/de/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/de/homepage.yml +++ b/de/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 70a57828b2eaa8fbd869c3000732f8932fe81f94 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:02 +0900 Subject: [PATCH 1350/1932] New translations homepage.yml (Greek) --- el/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/el/homepage.yml b/el/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/el/homepage.yml +++ b/el/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 165b947ab3b18a31b5ca8ff9cea2b9460c13d0c0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:03 +0900 Subject: [PATCH 1351/1932] New translations homepage.yml (Finnish) --- fi/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/fi/homepage.yml b/fi/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/fi/homepage.yml +++ b/fi/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 2e24126bc78656c469865e698bd8cfe7a9edf736 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:04 +0900 Subject: [PATCH 1352/1932] New translations homepage.yml (Hebrew) --- he/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/he/homepage.yml b/he/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/he/homepage.yml +++ b/he/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 2220417467cd62262f2c628c1c079bb86f81ab02 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:05 +0900 Subject: [PATCH 1353/1932] New translations homepage.yml (Italian) --- it/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/it/homepage.yml b/it/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/it/homepage.yml +++ b/it/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From f953c6a3a8f0b54fb46c1d9343996948100a1e53 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:06 +0900 Subject: [PATCH 1354/1932] New translations homepage.yml (Ukrainian) --- uk/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/uk/homepage.yml b/uk/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/uk/homepage.yml +++ b/uk/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From fe79ddb3b592375c07473887cd843fca53dd09f0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:07 +0900 Subject: [PATCH 1355/1932] New translations homepage.yml (Japanese) --- ja/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/ja/homepage.yml b/ja/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/ja/homepage.yml +++ b/ja/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From b2ee0e3c3da2dbdb6c9fdf26ee07697df7acc32c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:08 +0900 Subject: [PATCH 1356/1932] New translations homepage.yml (Korean) --- ko/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/ko/homepage.yml b/ko/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/ko/homepage.yml +++ b/ko/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From f9ed228bb6f27b3139f87174e1f75167766f0836 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:09 +0900 Subject: [PATCH 1357/1932] New translations homepage.yml (Dutch) --- nl/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/nl/homepage.yml b/nl/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/nl/homepage.yml +++ b/nl/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 61eee0995cf400c9a91a9dcdbbbff4dcd359dfcb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:10 +0900 Subject: [PATCH 1358/1932] New translations homepage.yml (Norwegian) --- no/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/no/homepage.yml b/no/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/no/homepage.yml +++ b/no/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 88086c1065f4bec543edc62985c4bf2e3ced2ede Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:11 +0900 Subject: [PATCH 1359/1932] New translations homepage.yml (Polish) --- pl/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/pl/homepage.yml b/pl/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/pl/homepage.yml +++ b/pl/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 6ba501f086b4161a7cb3a508c777616cefbec822 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:12 +0900 Subject: [PATCH 1360/1932] New translations homepage.yml (Russian) --- ru/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/ru/homepage.yml b/ru/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/ru/homepage.yml +++ b/ru/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From e393b9cf126313345c83002b2e9e68b9a562d7ce Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:14 +0900 Subject: [PATCH 1361/1932] New translations homepage.yml (Serbian (Cyrillic)) --- sr/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/sr/homepage.yml b/sr/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/sr/homepage.yml +++ b/sr/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 59bfc89bb4c753b4fcc668aad8dc029d1203cfd4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:15 +0900 Subject: [PATCH 1362/1932] New translations homepage.yml (Swedish) --- sv/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/sv/homepage.yml b/sv/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/sv/homepage.yml +++ b/sv/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From dc431b6c9b5ba1f1ded430f5f14e58a17b9dd710 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:16 +0900 Subject: [PATCH 1363/1932] New translations homepage.yml (Turkish) --- tr/homepage.yml | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/tr/homepage.yml b/tr/homepage.yml index 0493774c86b..34b73e3c64d 100644 --- a/tr/homepage.yml +++ b/tr/homepage.yml @@ -34,12 +34,6 @@ translations: - key: share.help_spread t: Help Spread the Word! - - - key: newsletter.stay_tuned - t: Don't Miss the Next Survey - - - key: newsletter.leave_your_email - t: Leave us your email and we’ll let you know when the next survey takes place. - key: homepage.other_surveys t: 'Other Surveys:' @@ -66,6 +60,12 @@ translations: t: Preview Questions - #newsletter + key: homepage.newsletter.stay_tuned + t: Don't Miss the Next Survey + - + key: homepage.newsletter.leave_your_email + t: Leave us your email and we’ll let you know when the next survey takes place. + - key: homepage.newsletter.email t: Your Email - @@ -78,3 +78,16 @@ translations: - key: languages.help_us_translate t: Help us translate the survey in your language → + - + #footer + key: homepage.made_by_devographics + aliasFor: general.made_by_devographics + - + key: homepage.netlify_link + aliasFor: general.netlify_link + - + key: homepage.leave_issue + aliasFor: general.leave_issue + - + key: homepage.join_discord + aliasFor: general.join_discord From 7be3e5d941b35c0d3c683093fb672301f77fc286 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:17 +0900 Subject: [PATCH 1364/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From c5448a358cb5f6b2e7078e88e2132c8ff88aa7b0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:18 +0900 Subject: [PATCH 1365/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 195b38319f2ad3613821a1abf2252353f594cb4b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:19 +0900 Subject: [PATCH 1366/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 48bc150b6669ff1ecacf1e42a07bb14373e1c195 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:20 +0900 Subject: [PATCH 1367/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From c4896413b96d826dd28e7f97e17f015072e936f9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:21 +0900 Subject: [PATCH 1368/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 8d4ba8443cf9e21d4fd5efdf0095bd7d84c82055 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:23 +0900 Subject: [PATCH 1369/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 15fb38ae5b0a2a0eb17176d2e45a8430b73281d3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:24 +0900 Subject: [PATCH 1370/1932] New translations state_of_graphql.yml (Chinese Simplified) --- zh/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From 4126928311053f0c14d1932f752ae9eff9ae5ed8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:26 +0900 Subject: [PATCH 1371/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From d357354c0aa426f5cadfcbb70e22b0393f166969 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 12:23:27 +0900 Subject: [PATCH 1372/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index 2a96d8af9d4..c6dc846e88c 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -166,6 +166,9 @@ translations: - key: features.disabling_introspection t: Disabling Introspection + - + key: features.disabling_introspection.description + t: Disabling introspection in production. - key: features.ip_allowlisting t: IP Allow-listing From c37f1f7255f9a89d3c45dd78a41cc15db8def0fa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:33 +0900 Subject: [PATCH 1373/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 353b5066f53bd5102b1df145fcf61284fbad4a64 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:34 +0900 Subject: [PATCH 1374/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From fe37bd0d8b0fa031425cdb77fbafa95b504f9c4a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:36 +0900 Subject: [PATCH 1375/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From fd1c585cc38ea589164db4980ea6cca082171a75 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:38 +0900 Subject: [PATCH 1376/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 02a460bcdc91200a9594904f84d54b49be5195b8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:40 +0900 Subject: [PATCH 1377/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 8c3c86e8036266cc7568bd76cf6479a41920dbcd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:42 +0900 Subject: [PATCH 1378/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 3a3fa36040a216c18cdd35f6f2f2c2d764e22860 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:45 +0900 Subject: [PATCH 1379/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 68c7c09aaa8e3df5115c68f24a29e2e438dccc40 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:47 +0900 Subject: [PATCH 1380/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 3e20fc3680fde4a1d509ddc5abd6d8399bbbad9d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:49 +0900 Subject: [PATCH 1381/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From bca450a6180cfd6de7f6bb3c0dfffd98bba4a07c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:50 +0900 Subject: [PATCH 1382/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 9f3a085b60d346c162e29e5c8f6df8cf352fcfc4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:51 +0900 Subject: [PATCH 1383/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 6c9f0c2e7c429f10f4b622104707b7535d70af6d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:52 +0900 Subject: [PATCH 1384/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 3fdb8fa624731fd1848a9096df7cc9a35181ed3a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:53 +0900 Subject: [PATCH 1385/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From b1dcfa890f73c1ccb3111c4d5f07e802049246b1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:54 +0900 Subject: [PATCH 1386/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 5c8919afbc0ed10eee46db4e3707f2b689758c03 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:55 +0900 Subject: [PATCH 1387/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 08f40c2627779569568050c5b32bf3c42c543227 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:56 +0900 Subject: [PATCH 1388/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From f9279e07fd96068f645b25f0f7bf724ccc697254 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:58 +0900 Subject: [PATCH 1389/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From f9c99818566d39e457a733720fbaad5cd7a0c606 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:00:59 +0900 Subject: [PATCH 1390/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 3a7529aca0c63dd8e627ddbe1e64be6fd8c105ce Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:01:01 +0900 Subject: [PATCH 1391/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From dadeefcc49568da3d3d3457c6647b3f7205e0b6a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:01:03 +0900 Subject: [PATCH 1392/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 86a445d565de8461a49d243a6019678499fd63de Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:01:04 +0900 Subject: [PATCH 1393/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 82a2137ea81b1052494ed5fce51ba7540f247343 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:01:05 +0900 Subject: [PATCH 1394/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 7143a71fcbf824305802d901859075edbf851ddf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:01:07 +0900 Subject: [PATCH 1395/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 9f7c25c6bec9e6f0e65265fb6666c7df129c3343 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:01:08 +0900 Subject: [PATCH 1396/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 64fdee65ba71c43ad00248bec8c372331ff891b8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:01:09 +0900 Subject: [PATCH 1397/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From cc4531999c892dd14c68cf9fc34024dbc63ae423 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:01:10 +0900 Subject: [PATCH 1398/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 92cef1178e9246cae1f414c4e021148435f1b3f8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:01:12 +0900 Subject: [PATCH 1399/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From 915acb3ed590f872b532fa5f0ccbc6f681b89764 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 15 Jun 2022 16:01:13 +0900 Subject: [PATCH 1400/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index c6dc846e88c..c7ba822724d 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -51,7 +51,7 @@ translations: t: Security & Performance - key: sections.security_performance.description - t: Making your API more robuts. + t: Making your API more robust. - key: sections.graphql_servers.title t: GraphQL Servers From f997011b9d80c86fa5da27f6ec48b7a58e3f1278 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:21 +0900 Subject: [PATCH 1401/1932] New translations common.yml (Romanian) --- ro/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ro/common.yml b/ro/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 8ad2090b079d68889666a655ba22d5eb614dd0d7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:22 +0900 Subject: [PATCH 1402/1932] New translations common.yml (Dutch) --- nl/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/nl/common.yml b/nl/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 64317c3f991ec777e929ef5f78b74cc27624c5e0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:23 +0900 Subject: [PATCH 1403/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/vi/common.yml b/vi/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 2d9240036e22eb8b155878f76b37c8bde8e53fca Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:24 +0900 Subject: [PATCH 1404/1932] New translations common.yml (English) --- en/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/en/common.yml b/en/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/en/common.yml +++ b/en/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 4bbfa9e85ef26b4990dedbe6c7585cae72f395ed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:25 +0900 Subject: [PATCH 1405/1932] New translations common.yml (Chinese Traditional) --- zh/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/zh/common.yml b/zh/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From f4a568bd886e081945cd53367672a0836df8e575 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:27 +0900 Subject: [PATCH 1406/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/uk/common.yml b/uk/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 20bf913727e5f9c970aaa0ecde098191c5b49dbc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:29 +0900 Subject: [PATCH 1407/1932] New translations common.yml (Turkish) --- tr/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/tr/common.yml b/tr/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 032b09c039f51ac711b276d1d6e337d377563fc3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:30 +0900 Subject: [PATCH 1408/1932] New translations common.yml (Swedish) --- sv/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/sv/common.yml b/sv/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 958ac425e1fc4498c8ebbad0a75d32553ba7f6db Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:31 +0900 Subject: [PATCH 1409/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/sr/common.yml b/sr/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From dbbdfdbb3484c6c2857b63fbef2e8624544c61b4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:33 +0900 Subject: [PATCH 1410/1932] New translations common.yml (Russian) --- ru/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ru/common.yml b/ru/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 55e22091128d52f02c7060d25d1f3832812d0dd7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:34 +0900 Subject: [PATCH 1411/1932] New translations common.yml (Portuguese) --- pt/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pt/common.yml b/pt/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 4db0a74ea2375ebfe8e028774cb2ad9b7b936bb3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:35 +0900 Subject: [PATCH 1412/1932] New translations common.yml (Polish) --- pl/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pl/common.yml b/pl/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From bcc67a67c2dc0904d4470387d2ff6dc13e3db021 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:37 +0900 Subject: [PATCH 1413/1932] New translations common.yml (Norwegian) --- no/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/no/common.yml b/no/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/no/common.yml +++ b/no/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From f66b4e29efb5bbacd4661437e8eb93ac7fcb612d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:38 +0900 Subject: [PATCH 1414/1932] New translations common.yml (Korean) --- ko/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ko/common.yml b/ko/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From de64dba604e18a2fc940cad83da87390aa2eca02 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:39 +0900 Subject: [PATCH 1415/1932] New translations common.yml (French) --- fr/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/fr/common.yml b/fr/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 058fffad9e1bb54d93cc6cd65940715bbb9adec6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:40 +0900 Subject: [PATCH 1416/1932] New translations common.yml (Japanese) --- ja/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ja/common.yml b/ja/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From bc2f69ff69173366909a8bea5badaf4da1cad8ee Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:41 +0900 Subject: [PATCH 1417/1932] New translations common.yml (Italian) --- it/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/it/common.yml b/it/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/it/common.yml +++ b/it/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 6e4b5dada6ddf94f8646dc9ad84a278d3d87dd74 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:42 +0900 Subject: [PATCH 1418/1932] New translations common.yml (Hungarian) --- hu/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/hu/common.yml b/hu/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 5c21441325cf16e82ee91651df1f99acc252acae Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:44 +0900 Subject: [PATCH 1419/1932] New translations common.yml (Hebrew) --- he/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/he/common.yml b/he/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/he/common.yml +++ b/he/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 314dfb829b5f3a46637e2879424c71e6051144d9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:46 +0900 Subject: [PATCH 1420/1932] New translations common.yml (Finnish) --- fi/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/fi/common.yml b/fi/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 5feab6ef3cea05c3eae2512dd0baf7d2c0079da2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:47 +0900 Subject: [PATCH 1421/1932] New translations common.yml (Greek) --- el/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/el/common.yml b/el/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/el/common.yml +++ b/el/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 53a09d5dd3ad20e75942cf0141040dfa982770d7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:49 +0900 Subject: [PATCH 1422/1932] New translations common.yml (German) --- de/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/de/common.yml b/de/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/de/common.yml +++ b/de/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From a5effdd41a3089e834395053bc787b14b04bf56e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:50 +0900 Subject: [PATCH 1423/1932] New translations common.yml (Danish) --- da/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/da/common.yml b/da/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/da/common.yml +++ b/da/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From ab451f4b752e4b2d5a261b0eeb4af2a5933e3113 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:51 +0900 Subject: [PATCH 1424/1932] New translations common.yml (Czech) --- cs/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/cs/common.yml b/cs/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From b685d736fac025116cf1a706b6d372266737db75 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:52 +0900 Subject: [PATCH 1425/1932] New translations common.yml (Catalan) --- ca/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ca/common.yml b/ca/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 8e01303411bdbec8f75e649a39cb7dc921390c05 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:53 +0900 Subject: [PATCH 1426/1932] New translations common.yml (Arabic) --- ar/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ar/common.yml b/ar/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From fc25d2159a15ed58f2c3e96f07c3afa8ea072495 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:54 +0900 Subject: [PATCH 1427/1932] New translations common.yml (Afrikaans) --- af/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/af/common.yml b/af/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/af/common.yml +++ b/af/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 3e817eb7b45afa2acfa7b5575a89ae04c7e70ecc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 16 Jun 2022 16:11:55 +0900 Subject: [PATCH 1428/1932] New translations common.yml (Spanish) --- es/common.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/es/common.yml b/es/common.yml index 00abe03cf58..0680a6972dd 100644 --- a/es/common.yml +++ b/es/common.yml @@ -448,13 +448,13 @@ translations: t: 25-34 years old - key: options.age.range_35_44 - t: 36-44 years old + t: 35-44 years old - key: options.age.range_45_54 - t: 46-54 years old + t: 45-54 years old - key: options.age.range_55_64 - t: 56-64 years old + t: 55-64 years old - key: options.age.range_more_than_65 t: 65 years or older @@ -473,13 +473,13 @@ translations: t: 25-34 - key: options.age.range_35_44.short - t: 36-44 + t: 35-44 - key: options.age.range_45_54.short - t: 46-54 + t: 45-54 - key: options.age.range_55_64.short - t: 56-64 + t: 55-64 - key: options.age.range_more_than_65.short t: '>65' From 5e1b249f6d23942cc843afb297b8166bbaa0e7f3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:22:54 +0900 Subject: [PATCH 1429/1932] New translations common.yml (Romanian) --- ro/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ro/common.yml b/ro/common.yml index 0680a6972dd..954987249b3 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From b024af35e875310f08e493a04dc5e6985354e6a2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:22:56 +0900 Subject: [PATCH 1430/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From d7de57ee229371325dbffba2a99722c1ed508cc1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:22:57 +0900 Subject: [PATCH 1431/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/vi/common.yml b/vi/common.yml index 0680a6972dd..954987249b3 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 34823559906d196b656764e246374b1a4e4901b7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:22:58 +0900 Subject: [PATCH 1432/1932] New translations common.yml (Portuguese, Brazilian) --- pt/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pt/common.yml b/pt/common.yml index 0680a6972dd..954987249b3 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 81c658fc84b52569771a97bf7e08acdbb25ad2f3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:00 +0900 Subject: [PATCH 1433/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 9fe9e2f47d5f979d5322f469201093c779a3f35e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:01 +0900 Subject: [PATCH 1434/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From df3f8fa4029849d52ab4b2eee28c47724b6d0a3d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:03 +0900 Subject: [PATCH 1435/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 4d368bb9314ae0f0e9f42605af006698a6a7415d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:04 +0900 Subject: [PATCH 1436/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From cd98bd618fb0197f09a09dcb3a2f72d407726977 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:05 +0900 Subject: [PATCH 1437/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 29744c1ff4c50cf00e72956d43428ac55ff1f448 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:06 +0900 Subject: [PATCH 1438/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From a9519637d2e34ee85e8bf5ec0014506a59dc8e94 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:07 +0900 Subject: [PATCH 1439/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From bfe9684d80cc521d5bb8af6ef575d70e8036a736 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:08 +0900 Subject: [PATCH 1440/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 9b7f77cb1629b3e3938a5a56bf3dd3a5692f6352 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:09 +0900 Subject: [PATCH 1441/1932] New translations common.yml (Chinese Traditional) --- zh/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/zh/common.yml b/zh/common.yml index 0680a6972dd..954987249b3 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 37ce7900efd81dfa6e3281c79dbef391d97e9744 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:12 +0900 Subject: [PATCH 1442/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From e216560d90a648af57345ce0b5bc29e706992f3e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:13 +0900 Subject: [PATCH 1443/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 0cc0bca337cd1fbd8ca20edf1a74135125699330 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:14 +0900 Subject: [PATCH 1444/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 048949710d1098bd3417a6a91765d66a1313ee52 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:15 +0900 Subject: [PATCH 1445/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 4ae8e0ad3c5b7843c6f65d171f9144bf1e62254d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:16 +0900 Subject: [PATCH 1446/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 39b29700ecdd3cd86222d85fa3588bfb9320bbe4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:17 +0900 Subject: [PATCH 1447/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 60d5a962a739b7d3390b1fd5dcb2ad055b135169 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:18 +0900 Subject: [PATCH 1448/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 8c072cb1463319859d6510e4473f48d56a1ffbe9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:19 +0900 Subject: [PATCH 1449/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 90bb49c8164624d761205aca1f426a2c778b870b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:20 +0900 Subject: [PATCH 1450/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 6be582a94e69ffa9e9d97fe03e18e73601ba0dff Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:21 +0900 Subject: [PATCH 1451/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 15ef7d57909eab1782d463a672f3a6387bd3d8af Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:23 +0900 Subject: [PATCH 1452/1932] New translations common.yml (English) --- en/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/en/common.yml b/en/common.yml index 0680a6972dd..954987249b3 100644 --- a/en/common.yml +++ b/en/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 11ee8cceb0e115fce7be06785439fe517f0536a3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:24 +0900 Subject: [PATCH 1453/1932] New translations common.yml (French) --- fr/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/fr/common.yml b/fr/common.yml index 0680a6972dd..954987249b3 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 2e40f564fe344fee55cf9694a24c02b7248e87db Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:26 +0900 Subject: [PATCH 1454/1932] New translations common.yml (Hungarian) --- hu/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/hu/common.yml b/hu/common.yml index 0680a6972dd..954987249b3 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 2e15c87b47ed9b6312881890054200c381291f31 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:27 +0900 Subject: [PATCH 1455/1932] New translations common.yml (Spanish) --- es/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/es/common.yml b/es/common.yml index 0680a6972dd..954987249b3 100644 --- a/es/common.yml +++ b/es/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 2c819ef53827e7a549e1ebdf4fb4a2612de3e02e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:28 +0900 Subject: [PATCH 1456/1932] New translations common.yml (Afrikaans) --- af/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/af/common.yml b/af/common.yml index 0680a6972dd..954987249b3 100644 --- a/af/common.yml +++ b/af/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 03cbf57e6d2287c5f143d7b54a874d35146e47b3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:29 +0900 Subject: [PATCH 1457/1932] New translations common.yml (Arabic) --- ar/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ar/common.yml b/ar/common.yml index 0680a6972dd..954987249b3 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 3320ad6826a5f7bb0878e6292441a32b54e72534 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:30 +0900 Subject: [PATCH 1458/1932] New translations common.yml (Catalan) --- ca/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ca/common.yml b/ca/common.yml index 0680a6972dd..954987249b3 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 2838b14bc65643c214b624dc0c8b856cd9662b91 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:32 +0900 Subject: [PATCH 1459/1932] New translations common.yml (Czech) --- cs/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/cs/common.yml b/cs/common.yml index 0680a6972dd..954987249b3 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From b834260daf704879fb0df1657e80526245b5a31b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:33 +0900 Subject: [PATCH 1460/1932] New translations common.yml (Danish) --- da/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/da/common.yml b/da/common.yml index 0680a6972dd..954987249b3 100644 --- a/da/common.yml +++ b/da/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From ffb3c4ad60e1cbb724251447c309903aa5fdfbea Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:34 +0900 Subject: [PATCH 1461/1932] New translations common.yml (German) --- de/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/de/common.yml b/de/common.yml index 0680a6972dd..954987249b3 100644 --- a/de/common.yml +++ b/de/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 5ceed04b33a897d01e6a659eaf894bdfae556b6d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:35 +0900 Subject: [PATCH 1462/1932] New translations common.yml (Greek) --- el/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/el/common.yml b/el/common.yml index 0680a6972dd..954987249b3 100644 --- a/el/common.yml +++ b/el/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From dbfecc642e107e5b9ea025cdfd048e6107d68461 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:36 +0900 Subject: [PATCH 1463/1932] New translations common.yml (Finnish) --- fi/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/fi/common.yml b/fi/common.yml index 0680a6972dd..954987249b3 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From d36f782d85def0cea711745d3bd50dde5f2778cc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:38 +0900 Subject: [PATCH 1464/1932] New translations common.yml (Hebrew) --- he/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/he/common.yml b/he/common.yml index 0680a6972dd..954987249b3 100644 --- a/he/common.yml +++ b/he/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From f4f909d6a9190d416d198da8bec4e38fe692723a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:39 +0900 Subject: [PATCH 1465/1932] New translations common.yml (Italian) --- it/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/it/common.yml b/it/common.yml index 0680a6972dd..954987249b3 100644 --- a/it/common.yml +++ b/it/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From f4d536af2e2be0feeb38eff39e74457796bca836 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:40 +0900 Subject: [PATCH 1466/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/uk/common.yml b/uk/common.yml index 0680a6972dd..954987249b3 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From af56c305233232e79ef6c7e8f5ac332f78298771 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:41 +0900 Subject: [PATCH 1467/1932] New translations common.yml (Japanese) --- ja/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ja/common.yml b/ja/common.yml index 0680a6972dd..954987249b3 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From f654e0ec7ebccf2f8b7c2caab718bb8cacae159d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:42 +0900 Subject: [PATCH 1468/1932] New translations common.yml (Korean) --- ko/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ko/common.yml b/ko/common.yml index 0680a6972dd..954987249b3 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 1c5eee69555d193212eb3347815345dc7efb921d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:45 +0900 Subject: [PATCH 1469/1932] New translations common.yml (Dutch) --- nl/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/nl/common.yml b/nl/common.yml index 0680a6972dd..954987249b3 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 46619a4eabebdbd440a6da93b355724aef57a55e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:46 +0900 Subject: [PATCH 1470/1932] New translations common.yml (Norwegian) --- no/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/no/common.yml b/no/common.yml index 0680a6972dd..954987249b3 100644 --- a/no/common.yml +++ b/no/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From dae23e9b97cb9a340e7f156a6b88f3013b92b7c3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:47 +0900 Subject: [PATCH 1471/1932] New translations common.yml (Polish) --- pl/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pl/common.yml b/pl/common.yml index 0680a6972dd..954987249b3 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From a200aba7d9bbaf803ce9de9d4a5f876e4667c8b1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:49 +0900 Subject: [PATCH 1472/1932] New translations common.yml (Russian) --- ru/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ru/common.yml b/ru/common.yml index 0680a6972dd..954987249b3 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 82d7ddf8abffc00dda9e896cf3b043a8176e6d5e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:50 +0900 Subject: [PATCH 1473/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/sr/common.yml b/sr/common.yml index 0680a6972dd..954987249b3 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From de52068a18f8efc86e540a37de69616274487657 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:53 +0900 Subject: [PATCH 1474/1932] New translations common.yml (Swedish) --- sv/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/sv/common.yml b/sv/common.yml index 0680a6972dd..954987249b3 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 69aa2cc0a050f200fbe448e33c8a2ef6a5d8e8b4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:54 +0900 Subject: [PATCH 1475/1932] New translations common.yml (Turkish) --- tr/common.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tr/common.yml b/tr/common.yml index 0680a6972dd..954987249b3 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -1290,6 +1290,10 @@ translations: key: user_info.email_temporary.note t: > We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: how_can_we_improve + t: How could we improve this survey? - ########################################################################### #Other Tools From 2c05a3bf6e220fa2f74ec6f2f743611fb4a6c28b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:55 +0900 Subject: [PATCH 1476/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 340e343759c452a84edb881331ccfe785f1e9a56 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:57 +0900 Subject: [PATCH 1477/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From e322e1ace8be7c60fc6b889bf21c2fe228056e52 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:58 +0900 Subject: [PATCH 1478/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From d578ba309ef64c33bc3ff3e04a48b481b57c44dc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:23:59 +0900 Subject: [PATCH 1479/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 4e77a2c552651ca8cbbb976942b01fc8c38bb789 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:24:00 +0900 Subject: [PATCH 1480/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 0a348226b121b926523c5fddeb373bdb4bfe1cc0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:24:01 +0900 Subject: [PATCH 1481/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 10e81568c3be7962ccc5fbd847eaec2941fb768c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:24:02 +0900 Subject: [PATCH 1482/1932] New translations state_of_graphql.yml (Chinese Simplified) --- zh/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From ede2a4369b84abe9cadd1c58fb9e5429cf1ca2eb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:24:04 +0900 Subject: [PATCH 1483/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 4e5a085edfc2f52d3e076fa91312c384d36b73d3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Fri, 17 Jun 2022 16:24:05 +0900 Subject: [PATCH 1484/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 9 --------- 1 file changed, 9 deletions(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index c7ba822724d..084a8d80788 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -224,15 +224,6 @@ translations: - key: other_tools.combining_schemas.others t: Other tools for combining schemas - - - key: other_tools.server_languages - t: Server Languages - - - key: other_tools.server_languages.description - t: Which language(s) do you use to write your GraphQL back-ends? - - - key: other_tools.server_languages - t: Other Server Languages - key: other_tools.graphql_ides t: GraphQL IDEs From 62307023092330d9576d87b12bf0fb2fd8cae164 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:19:57 +0900 Subject: [PATCH 1485/1932] New translations common.yml (Romanian) --- ro/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ro/common.yml b/ro/common.yml index 954987249b3..cbea1b4487e 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 13502651894b3181f341a7443290800b89e06b1f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:19:58 +0900 Subject: [PATCH 1486/1932] New translations common.yml (Dutch) --- nl/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/nl/common.yml b/nl/common.yml index 954987249b3..cbea1b4487e 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From eb1000c715314691966a4749b33511efa033fd4c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:19:59 +0900 Subject: [PATCH 1487/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/vi/common.yml b/vi/common.yml index 954987249b3..cbea1b4487e 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From ebad5574ff7386a5a0ab231c5c4ff3070db59ed1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:00 +0900 Subject: [PATCH 1488/1932] New translations common.yml (English) --- en/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/en/common.yml b/en/common.yml index 954987249b3..cbea1b4487e 100644 --- a/en/common.yml +++ b/en/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From a5c5200a13ead061cffea5bbe5d6ca357a19a850 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:02 +0900 Subject: [PATCH 1489/1932] New translations common.yml (Chinese Traditional) --- zh/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/zh/common.yml b/zh/common.yml index 954987249b3..cbea1b4487e 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 40b5a746832f8fe187f0abf69122a531c53cf8fc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:05 +0900 Subject: [PATCH 1490/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/uk/common.yml b/uk/common.yml index 954987249b3..cbea1b4487e 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 6ea2133a110fa48fa031e650c5b5e6f3116283b9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:06 +0900 Subject: [PATCH 1491/1932] New translations common.yml (Turkish) --- tr/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tr/common.yml b/tr/common.yml index 954987249b3..cbea1b4487e 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From f49f009dd615493179a4b563e204cc5691790cf6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:07 +0900 Subject: [PATCH 1492/1932] New translations common.yml (Swedish) --- sv/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/sv/common.yml b/sv/common.yml index 954987249b3..cbea1b4487e 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 19a9316a793520abdcca4e0c7c725a4dc1949e0f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:10 +0900 Subject: [PATCH 1493/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/sr/common.yml b/sr/common.yml index 954987249b3..cbea1b4487e 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 6a6950e8535998393f1d77ed03990b0d8fb888f2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:11 +0900 Subject: [PATCH 1494/1932] New translations common.yml (Russian) --- ru/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ru/common.yml b/ru/common.yml index 954987249b3..cbea1b4487e 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 6aa90b8a017e8e0df0b0ff1ef2243958832f0030 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:12 +0900 Subject: [PATCH 1495/1932] New translations common.yml (Portuguese) --- pt/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pt/common.yml b/pt/common.yml index 954987249b3..cbea1b4487e 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 81ea184d07cfc19c05842432fc6c38174c813f26 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:13 +0900 Subject: [PATCH 1496/1932] New translations common.yml (Polish) --- pl/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pl/common.yml b/pl/common.yml index 954987249b3..cbea1b4487e 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 007e5e30ac254bc10bf4d23a775e5a57cf599d7d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:14 +0900 Subject: [PATCH 1497/1932] New translations common.yml (Norwegian) --- no/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/no/common.yml b/no/common.yml index 954987249b3..cbea1b4487e 100644 --- a/no/common.yml +++ b/no/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 384316c25a43c27d45d40dd9f9d9ac345cf153c3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:16 +0900 Subject: [PATCH 1498/1932] New translations common.yml (Korean) --- ko/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ko/common.yml b/ko/common.yml index 954987249b3..cbea1b4487e 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From c18b24185ace29c76c05656da05cd11cfc1972b8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:17 +0900 Subject: [PATCH 1499/1932] New translations common.yml (French) --- fr/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fr/common.yml b/fr/common.yml index 954987249b3..cbea1b4487e 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From a08f9f4aa8b3cf121cb29feca237127b27c74094 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:18 +0900 Subject: [PATCH 1500/1932] New translations common.yml (Japanese) --- ja/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ja/common.yml b/ja/common.yml index 954987249b3..cbea1b4487e 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 6a13017505ca5fe2b45499c27ebb6617e4ca08ed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:19 +0900 Subject: [PATCH 1501/1932] New translations common.yml (Italian) --- it/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/it/common.yml b/it/common.yml index 954987249b3..cbea1b4487e 100644 --- a/it/common.yml +++ b/it/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From f0cbf13fceb355722f34f790813a2e1bd6e6d22b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:20 +0900 Subject: [PATCH 1502/1932] New translations common.yml (Hungarian) --- hu/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/hu/common.yml b/hu/common.yml index 954987249b3..cbea1b4487e 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From d66bef7d8df3e68dbe0a6a1f165457691be76f38 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:21 +0900 Subject: [PATCH 1503/1932] New translations common.yml (Hebrew) --- he/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/he/common.yml b/he/common.yml index 954987249b3..cbea1b4487e 100644 --- a/he/common.yml +++ b/he/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 9afeee75e46aabf9e40981527ba3f2852a043364 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:22 +0900 Subject: [PATCH 1504/1932] New translations common.yml (Finnish) --- fi/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fi/common.yml b/fi/common.yml index 954987249b3..cbea1b4487e 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 075f5fba44554554c5c25a40663e57df317e08b1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:23 +0900 Subject: [PATCH 1505/1932] New translations common.yml (Greek) --- el/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/el/common.yml b/el/common.yml index 954987249b3..cbea1b4487e 100644 --- a/el/common.yml +++ b/el/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From d1a2264ba0bf9540be0dd381c4f4ab093ec0406f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:25 +0900 Subject: [PATCH 1506/1932] New translations common.yml (German) --- de/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/de/common.yml b/de/common.yml index 954987249b3..cbea1b4487e 100644 --- a/de/common.yml +++ b/de/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 82f3231990a859e5748544625eaa090ae342056d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:26 +0900 Subject: [PATCH 1507/1932] New translations common.yml (Danish) --- da/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/da/common.yml b/da/common.yml index 954987249b3..cbea1b4487e 100644 --- a/da/common.yml +++ b/da/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From a88856a47b889c243b00f619e36be67f77d9133e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:27 +0900 Subject: [PATCH 1508/1932] New translations common.yml (Czech) --- cs/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/cs/common.yml b/cs/common.yml index 954987249b3..cbea1b4487e 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 654ef67f92e25ac29db63b34aea89e99f04b6d8c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:28 +0900 Subject: [PATCH 1509/1932] New translations common.yml (Catalan) --- ca/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ca/common.yml b/ca/common.yml index 954987249b3..cbea1b4487e 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 4d2f2f8fa2cc7f1e41bce72b00c02cb7de5417c8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:29 +0900 Subject: [PATCH 1510/1932] New translations common.yml (Arabic) --- ar/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ar/common.yml b/ar/common.yml index 954987249b3..cbea1b4487e 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From ed17503368131081dd4c6063aaef7c7e495fd088 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:30 +0900 Subject: [PATCH 1511/1932] New translations common.yml (Afrikaans) --- af/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/af/common.yml b/af/common.yml index 954987249b3..cbea1b4487e 100644 --- a/af/common.yml +++ b/af/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From ad267c6534a2cf213ac4cc8fd1087ab88c55451c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 10:20:31 +0900 Subject: [PATCH 1512/1932] New translations common.yml (Spanish) --- es/common.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/es/common.yml b/es/common.yml index 954987249b3..cbea1b4487e 100644 --- a/es/common.yml +++ b/es/common.yml @@ -1292,7 +1292,7 @@ translations: We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. - #how can we improve the survey? - key: how_can_we_improve + key: user_info.how_can_we_improve t: How could we improve this survey? - ########################################################################### @@ -1461,3 +1461,6 @@ translations: - key: resources.other_surveys.description t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From ab1fa49ed22bd94504a32d5e511072db9e1ffdd8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:57:54 +0900 Subject: [PATCH 1513/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From e7654d0b9d9db61633afebc49b5448bb45e1ccdc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:57:55 +0900 Subject: [PATCH 1514/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 5421da097564aba1b3da4d52034aab2929a7ebb2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:57:56 +0900 Subject: [PATCH 1515/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From f38261dfdd2bf7f70febcad2885afbe7590437eb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:57:57 +0900 Subject: [PATCH 1516/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 5eab8a44698c6e5b0677a06fa136ca7fc05d1584 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:57:58 +0900 Subject: [PATCH 1517/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 57461d65b46df6e96f9425fb798419266ec96e28 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:57:59 +0900 Subject: [PATCH 1518/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 374071edd1370b7ffd12165075858d2c3ea336f0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:00 +0900 Subject: [PATCH 1519/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 3f59c3f1e99a74cdda41bfa6253ab9ae1a5ee4d2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:01 +0900 Subject: [PATCH 1520/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From f7f70f42344bc014c44c207294dc871934848421 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:02 +0900 Subject: [PATCH 1521/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From b18e0585431e3faab109ece8f44c8dce01c4bcfa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:03 +0900 Subject: [PATCH 1522/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 02beb14a3540e48303ea6de073c758201045b7cd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:04 +0900 Subject: [PATCH 1523/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 18f7eea06b426ef381f4ed66f01c1b7f9b230aeb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:05 +0900 Subject: [PATCH 1524/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From b6e1beb66709eb657a76b55aa524523639e5e64e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:06 +0900 Subject: [PATCH 1525/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 0be13d17f3231086c5edfb32568ecad732f64d43 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:07 +0900 Subject: [PATCH 1526/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 0a815149ce634765d43092724cdaca9d0b8d7719 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:08 +0900 Subject: [PATCH 1527/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 7c0bccc5d1e0b14062d1f30c4a9952e9e6ce7f26 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:09 +0900 Subject: [PATCH 1528/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 1d70a8f3a33fc0ef6d461194df7fb1569676947a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:10 +0900 Subject: [PATCH 1529/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 110ba781595a215cd9a63d8ca839179f35921682 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:11 +0900 Subject: [PATCH 1530/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 36ffc66ca98c5fff44c0e3ebf482089a28d9845d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:12 +0900 Subject: [PATCH 1531/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From fc1ffb7af46aef801a05d29fbe5c5490da780fe9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:13 +0900 Subject: [PATCH 1532/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 05441cf4daf322b99de7dab3cbaef2ffaade63da Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:14 +0900 Subject: [PATCH 1533/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 89b8217428283013e263e4e925c11cc25c7121dd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:15 +0900 Subject: [PATCH 1534/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 1afb4251f0720566017bd958723e5f79c96b6b4e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:16 +0900 Subject: [PATCH 1535/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From b876cb9e0754f87f93da3eb03df32f90ccd44b15 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:17 +0900 Subject: [PATCH 1536/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 0f793546ceb3ed6b6b80b69f0eaac2f46b371f88 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:18 +0900 Subject: [PATCH 1537/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From b304c7dd81d99653607543c34448988803400b0d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:19 +0900 Subject: [PATCH 1538/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 7f1a5834e39816bf6770ecf660d3ed5f37dc7b00 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:20 +0900 Subject: [PATCH 1539/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From 11317d9ad92a80df0ce8008719195d07ac10a3e7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Wed, 22 Jun 2022 13:58:21 +0900 Subject: [PATCH 1540/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index 084a8d80788..ae1ab35b6af 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -360,6 +360,9 @@ translations: - key: resources.first_steps_graphql.description t: When first starting out, how did you initially learn GraphQL? + - + key: resources.first_steps_graphql.others + t: Other initial learning methods - #sites & courses key: resources.sites_courses From e88c8daf6407ee16759aceb47f9d9eea97b78a9f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:31 +0900 Subject: [PATCH 1541/1932] New translations state_of_css.yml (Romanian) --- ro/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/ro/state_of_css.yml b/ro/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/ro/state_of_css.yml +++ b/ro/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From b45d094d7b71b573270c8d050aa7bece0b37e1c5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:32 +0900 Subject: [PATCH 1542/1932] New translations state_of_css.yml (Dutch) --- nl/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/nl/state_of_css.yml b/nl/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/nl/state_of_css.yml +++ b/nl/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 0e068250d8cba46b435d7b6d8d6b5b7561ce68d6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:34 +0900 Subject: [PATCH 1543/1932] New translations state_of_css.yml (Vietnamese) --- vi/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/vi/state_of_css.yml b/vi/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/vi/state_of_css.yml +++ b/vi/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From ec48116e4b989f73e14f47f838a1ba77d12315b0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:35 +0900 Subject: [PATCH 1544/1932] New translations state_of_css.yml (English) --- en/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/en/state_of_css.yml b/en/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/en/state_of_css.yml +++ b/en/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 07faeffca714c8398e9337cdee26794f0a52964c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:35 +0900 Subject: [PATCH 1545/1932] New translations state_of_css.yml (Chinese Traditional) --- zh/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/zh/state_of_css.yml b/zh/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/zh/state_of_css.yml +++ b/zh/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 5769a7174f1e1ce087e88d3d4c4275f8b7e8dad0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:37 +0900 Subject: [PATCH 1546/1932] New translations state_of_css.yml (Ukrainian) --- uk/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/uk/state_of_css.yml b/uk/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/uk/state_of_css.yml +++ b/uk/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 8361e25e2237337134b041fb526e0fcbd46d0cb2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:38 +0900 Subject: [PATCH 1547/1932] New translations state_of_css.yml (Turkish) --- tr/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/tr/state_of_css.yml b/tr/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/tr/state_of_css.yml +++ b/tr/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 139be014eb3a822545fac992253a805e0dae4a8d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:39 +0900 Subject: [PATCH 1548/1932] New translations state_of_css.yml (Swedish) --- sv/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/sv/state_of_css.yml b/sv/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/sv/state_of_css.yml +++ b/sv/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From d898f6b427e075ad7a26565b3eeaf974bc13dfb0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:40 +0900 Subject: [PATCH 1549/1932] New translations state_of_css.yml (Serbian (Cyrillic)) --- sr/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/sr/state_of_css.yml b/sr/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/sr/state_of_css.yml +++ b/sr/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From b9ca029786a90fe3a8a6cc06a8e1e069601f8f40 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:41 +0900 Subject: [PATCH 1550/1932] New translations state_of_css.yml (Russian) --- ru/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/ru/state_of_css.yml b/ru/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/ru/state_of_css.yml +++ b/ru/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 23e3b67a407c305351f9a56163ac99c9fca46643 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:42 +0900 Subject: [PATCH 1551/1932] New translations state_of_css.yml (Portuguese) --- pt/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/pt/state_of_css.yml b/pt/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/pt/state_of_css.yml +++ b/pt/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From cabc95317ea5c202753471b2003fff23b98bf857 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:43 +0900 Subject: [PATCH 1552/1932] New translations state_of_css.yml (Polish) --- pl/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/pl/state_of_css.yml b/pl/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/pl/state_of_css.yml +++ b/pl/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 195289752e0ba9b3550737598283c39030769a51 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:44 +0900 Subject: [PATCH 1553/1932] New translations state_of_css.yml (Norwegian) --- no/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/no/state_of_css.yml b/no/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/no/state_of_css.yml +++ b/no/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 6205ef78b6b21f7701b33084eea51e32c71d2347 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:45 +0900 Subject: [PATCH 1554/1932] New translations state_of_css.yml (Korean) --- ko/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/ko/state_of_css.yml b/ko/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/ko/state_of_css.yml +++ b/ko/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 62b9fdaa4ccdb84ee20348efcdd715357e456f1e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:46 +0900 Subject: [PATCH 1555/1932] New translations state_of_css.yml (French) --- fr/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/fr/state_of_css.yml b/fr/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/fr/state_of_css.yml +++ b/fr/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 95f7623856ce0cfc88b63e070727726fa5d55a4b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:47 +0900 Subject: [PATCH 1556/1932] New translations state_of_css.yml (Japanese) --- ja/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/ja/state_of_css.yml b/ja/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/ja/state_of_css.yml +++ b/ja/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From dc631fbeda7e81db816073769be497ab67d71e1e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:48 +0900 Subject: [PATCH 1557/1932] New translations state_of_css.yml (Italian) --- it/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/it/state_of_css.yml b/it/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/it/state_of_css.yml +++ b/it/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 9d5855f7f9623cd8899a8bc9092f319df9b3ce5b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:49 +0900 Subject: [PATCH 1558/1932] New translations state_of_css.yml (Hungarian) --- hu/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/hu/state_of_css.yml b/hu/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/hu/state_of_css.yml +++ b/hu/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 72fcb01bf29323f1efd68c75c433accd8d15d1a5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:50 +0900 Subject: [PATCH 1559/1932] New translations state_of_css.yml (Hebrew) --- he/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/he/state_of_css.yml b/he/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/he/state_of_css.yml +++ b/he/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From cc756536c6739977a6e39f83d15c7b8cb7b571cd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:51 +0900 Subject: [PATCH 1560/1932] New translations state_of_css.yml (Finnish) --- fi/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/fi/state_of_css.yml b/fi/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/fi/state_of_css.yml +++ b/fi/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 9e110fce0ac30f9bf1ddc26e887384dcba485d87 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:52 +0900 Subject: [PATCH 1561/1932] New translations state_of_css.yml (Greek) --- el/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/el/state_of_css.yml b/el/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/el/state_of_css.yml +++ b/el/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 17257d32f1ab540df315e845d629cd47517458a5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:53 +0900 Subject: [PATCH 1562/1932] New translations state_of_css.yml (German) --- de/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/de/state_of_css.yml b/de/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/de/state_of_css.yml +++ b/de/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 2ca8c89954cc6fa3ac49f6f4906d17445b0ca31c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:54 +0900 Subject: [PATCH 1563/1932] New translations state_of_css.yml (Danish) --- da/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/da/state_of_css.yml b/da/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/da/state_of_css.yml +++ b/da/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From c1c15e0eee46c0c0c52077df81d1cf178f5c4d90 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:55 +0900 Subject: [PATCH 1564/1932] New translations state_of_css.yml (Czech) --- cs/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/cs/state_of_css.yml b/cs/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/cs/state_of_css.yml +++ b/cs/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 34b4a7a99b40ca90ee9ac73764a47838c6bcbe19 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:56 +0900 Subject: [PATCH 1565/1932] New translations state_of_css.yml (Catalan) --- ca/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/ca/state_of_css.yml b/ca/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/ca/state_of_css.yml +++ b/ca/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 1e3a1d3e7f19836b6eb7f2b2bb215fd5d872568e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:57 +0900 Subject: [PATCH 1566/1932] New translations state_of_css.yml (Arabic) --- ar/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/ar/state_of_css.yml b/ar/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/ar/state_of_css.yml +++ b/ar/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From d42f996c07fa6033492bc06a11fde1e6710237b7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:58 +0900 Subject: [PATCH 1567/1932] New translations state_of_css.yml (Afrikaans) --- af/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/af/state_of_css.yml b/af/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/af/state_of_css.yml +++ b/af/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From c5b6189b356f8968b9181bcea91cfb21b6060310 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Sun, 17 Jul 2022 18:44:59 +0900 Subject: [PATCH 1568/1932] New translations state_of_css.yml (Spanish) --- es/state_of_css.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/es/state_of_css.yml b/es/state_of_css.yml index 5b1690df2d9..adf8e76b721 100644 --- a/es/state_of_css.yml +++ b/es/state_of_css.yml @@ -61,6 +61,24 @@ translations: - key: sections.media_queries.description t: Ways of adapting your site to the user's device or preferences. + - + key: sections.selectors.title + t: Selectors + - + key: sections.selectors.description + t: CSS selectors. + - + key: sections.colors.title + t: Colors + - + key: sections.colors.description + t: Color-related features. + - + key: sections.javascript_apis.title + t: JavaScript APIs + - + key: sections.javascript_apis.description + t: JavaScript APIs used to control or complement CSS. - key: sections.other_features.title t: Other Features From 3518974e6020b092308e5e10f62573e874c8d913 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:17:50 +0900 Subject: [PATCH 1569/1932] New translations state_of_css.yml (Romanian) --- ro/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/ro/state_of_css.yml b/ro/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/ro/state_of_css.yml +++ b/ro/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From d2a3c538787f6d9b685faa8257248fed8af54133 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:17:51 +0900 Subject: [PATCH 1570/1932] New translations state_of_js.yml (Afrikaans) --- af/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/af/state_of_js.yml b/af/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/af/state_of_js.yml +++ b/af/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 56771334b2cffe41c12c27a37c4447cf6fafad43 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:17:52 +0900 Subject: [PATCH 1571/1932] New translations state_of_css.yml (Vietnamese) --- vi/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/vi/state_of_css.yml b/vi/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/vi/state_of_css.yml +++ b/vi/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 35a3026443a9ef7518eb482512f8a9b2aefac083 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:17:53 +0900 Subject: [PATCH 1572/1932] New translations state_of_css.yml (Portuguese, Brazilian) --- pt/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/pt/state_of_css.yml b/pt/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/pt/state_of_css.yml +++ b/pt/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 6c399ea0980aee6c54ac6870192fd9e4e651fdaa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:17:54 +0900 Subject: [PATCH 1573/1932] New translations common.yml (Romanian) --- ro/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ro/common.yml b/ro/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 4b57e20dd96d2dfd9e21e42a0206b6c00a414094 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:17:55 +0900 Subject: [PATCH 1574/1932] New translations state_of_js.yml (Romanian) --- ro/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ro/state_of_js.yml b/ro/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/ro/state_of_js.yml +++ b/ro/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 1ac6be6ecdaa6597b417ae893df4a00871c4d271 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:17:56 +0900 Subject: [PATCH 1575/1932] New translations common.yml (French) --- fr/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fr/common.yml b/fr/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From cefe246e317c67f27b7bf37e6733f26bdca2d18b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:17:57 +0900 Subject: [PATCH 1576/1932] New translations state_of_js.yml (French) --- fr/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fr/state_of_js.yml b/fr/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/fr/state_of_js.yml +++ b/fr/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 3758d6453886c83f67455bbc9e78161166932e8a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:17:58 +0900 Subject: [PATCH 1577/1932] New translations common.yml (Spanish) --- es/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es/common.yml b/es/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/es/common.yml +++ b/es/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 6830aea70dee43b600880476bf29c48c9c91521c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:17:59 +0900 Subject: [PATCH 1578/1932] New translations state_of_js.yml (Spanish) --- es/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/es/state_of_js.yml b/es/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/es/state_of_js.yml +++ b/es/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 4220eac1d0c37a275397c99a871cb68483b42b20 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:00 +0900 Subject: [PATCH 1579/1932] New translations common.yml (Afrikaans) --- af/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/af/common.yml b/af/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/af/common.yml +++ b/af/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 3977293919914ece7b56dd9092671043dd1170a8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:01 +0900 Subject: [PATCH 1580/1932] New translations common.yml (Arabic) --- ar/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ar/common.yml b/ar/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 50433e5983a6ade083eccfe1f2d08d7f965308f1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:02 +0900 Subject: [PATCH 1581/1932] New translations state_of_css.yml (Chinese Traditional) --- zh/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/zh/state_of_css.yml b/zh/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/zh/state_of_css.yml +++ b/zh/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 831467269ab9acf3ee43408835181dc069fd0fde Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:04 +0900 Subject: [PATCH 1582/1932] New translations state_of_js.yml (Arabic) --- ar/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ar/state_of_js.yml b/ar/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/ar/state_of_js.yml +++ b/ar/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From bb64e2ee4a221d30b695a2afc4d36e89a22ed164 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:05 +0900 Subject: [PATCH 1583/1932] New translations common.yml (Catalan) --- ca/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ca/common.yml b/ca/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 2de2d45f7b50e564b8171314c1737f215dce9a41 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:06 +0900 Subject: [PATCH 1584/1932] New translations state_of_js.yml (Catalan) --- ca/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ca/state_of_js.yml b/ca/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/ca/state_of_js.yml +++ b/ca/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 493fe05cc206a68fc3120eda46d7f3dc73eff9f5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:07 +0900 Subject: [PATCH 1585/1932] New translations common.yml (Czech) --- cs/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cs/common.yml b/cs/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 7c358635b6a4bca7d0b871adfacaf4ed2a24c19c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:08 +0900 Subject: [PATCH 1586/1932] New translations state_of_js.yml (Czech) --- cs/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cs/state_of_js.yml b/cs/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/cs/state_of_js.yml +++ b/cs/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From d89e2c705c9e4f8fa20e11b2f1d04cdbe600243d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:09 +0900 Subject: [PATCH 1587/1932] New translations common.yml (Danish) --- da/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/da/common.yml b/da/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/da/common.yml +++ b/da/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 323bc1d404c8175522f52aaadf7ec1e49d27745a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:10 +0900 Subject: [PATCH 1588/1932] New translations state_of_js.yml (Danish) --- da/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/da/state_of_js.yml b/da/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/da/state_of_js.yml +++ b/da/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From c866294ab9f5a9f350c9e1ac76dafcd0bc9f297e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:11 +0900 Subject: [PATCH 1589/1932] New translations common.yml (German) --- de/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/de/common.yml b/de/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/de/common.yml +++ b/de/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 728139821731a7c18bf01f3717e1e09abcc3db47 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:12 +0900 Subject: [PATCH 1590/1932] New translations state_of_js.yml (German) --- de/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/de/state_of_js.yml b/de/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/de/state_of_js.yml +++ b/de/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From f8a862afd2fc1c972d65a660dfba019fd42578f4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:13 +0900 Subject: [PATCH 1591/1932] New translations common.yml (Greek) --- el/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/el/common.yml b/el/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/el/common.yml +++ b/el/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 707b746013063ca870020f5ec355b2950886c495 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:14 +0900 Subject: [PATCH 1592/1932] New translations state_of_css.yml (English) --- en/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/en/state_of_css.yml b/en/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/en/state_of_css.yml +++ b/en/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From ee772435187a3b3079f61a90912b8b0be423835e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:16 +0900 Subject: [PATCH 1593/1932] New translations state_of_css.yml (French) --- fr/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/fr/state_of_css.yml b/fr/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/fr/state_of_css.yml +++ b/fr/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From cf57dfa7d7a33b06f53bcc23c000731da1094e3a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:17 +0900 Subject: [PATCH 1594/1932] New translations state_of_css.yml (Hungarian) --- hu/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/hu/state_of_css.yml b/hu/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/hu/state_of_css.yml +++ b/hu/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From ffa844b508abcd14765d79691f33413ed40c767e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:18 +0900 Subject: [PATCH 1595/1932] New translations state_of_css.yml (Spanish) --- es/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/es/state_of_css.yml b/es/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/es/state_of_css.yml +++ b/es/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 00875cc2fa4bb554315bb56e3fc5439e83b21ce2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:19 +0900 Subject: [PATCH 1596/1932] New translations state_of_css.yml (Afrikaans) --- af/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/af/state_of_css.yml b/af/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/af/state_of_css.yml +++ b/af/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 777f8b4f86cd895353d375f796f47bc24be65fe7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:20 +0900 Subject: [PATCH 1597/1932] New translations state_of_css.yml (Arabic) --- ar/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/ar/state_of_css.yml b/ar/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/ar/state_of_css.yml +++ b/ar/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From b1dcd66d2829494cfa0c671206415d6e58d3107a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:21 +0900 Subject: [PATCH 1598/1932] New translations state_of_css.yml (Catalan) --- ca/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/ca/state_of_css.yml b/ca/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/ca/state_of_css.yml +++ b/ca/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 5689d926dd36143b363d41c6f3b493b28f55088b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:22 +0900 Subject: [PATCH 1599/1932] New translations state_of_css.yml (Czech) --- cs/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/cs/state_of_css.yml b/cs/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/cs/state_of_css.yml +++ b/cs/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 45289db1b3c47649684f29ae3e9a0c54ae8a0647 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:23 +0900 Subject: [PATCH 1600/1932] New translations state_of_css.yml (Danish) --- da/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/da/state_of_css.yml b/da/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/da/state_of_css.yml +++ b/da/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From ff9fcd22eef5b0b99cb1b0f19c19bd0cf1a421c1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:24 +0900 Subject: [PATCH 1601/1932] New translations state_of_css.yml (German) --- de/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/de/state_of_css.yml b/de/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/de/state_of_css.yml +++ b/de/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 452e38d65d8c4feaa3657126f8c6566744a41ed9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:25 +0900 Subject: [PATCH 1602/1932] New translations state_of_css.yml (Greek) --- el/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/el/state_of_css.yml b/el/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/el/state_of_css.yml +++ b/el/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From f89c7cbee0320e6c5580a3347b2ccad88c597aca Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:26 +0900 Subject: [PATCH 1603/1932] New translations state_of_css.yml (Finnish) --- fi/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/fi/state_of_css.yml b/fi/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/fi/state_of_css.yml +++ b/fi/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 60562e80f7856e0d7933514f99e562a764b04a1e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:27 +0900 Subject: [PATCH 1604/1932] New translations state_of_css.yml (Hebrew) --- he/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/he/state_of_css.yml b/he/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/he/state_of_css.yml +++ b/he/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From ea4ec3e3e735391ca79bea99713e6c3142e08a69 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:28 +0900 Subject: [PATCH 1605/1932] New translations state_of_css.yml (Italian) --- it/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/it/state_of_css.yml b/it/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/it/state_of_css.yml +++ b/it/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From e6bfa501b9adfc19788257369b0020d828cbf221 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:29 +0900 Subject: [PATCH 1606/1932] New translations state_of_css.yml (Ukrainian) --- uk/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/uk/state_of_css.yml b/uk/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/uk/state_of_css.yml +++ b/uk/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 003c7a126f40e24d7825f2cce621e24939364714 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:31 +0900 Subject: [PATCH 1607/1932] New translations state_of_css.yml (Japanese) --- ja/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/ja/state_of_css.yml b/ja/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/ja/state_of_css.yml +++ b/ja/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 0365d2d2f04de3a234dba970316ddae341c09cab Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:32 +0900 Subject: [PATCH 1608/1932] New translations state_of_css.yml (Korean) --- ko/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/ko/state_of_css.yml b/ko/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/ko/state_of_css.yml +++ b/ko/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 63aa2b14bc20066212be7710f2a471754dae5a88 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:34 +0900 Subject: [PATCH 1609/1932] New translations state_of_css.yml (Dutch) --- nl/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/nl/state_of_css.yml b/nl/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/nl/state_of_css.yml +++ b/nl/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 59738a9ed1ac774f5037dd0bb2716d1cfaaa5efa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:35 +0900 Subject: [PATCH 1610/1932] New translations state_of_css.yml (Norwegian) --- no/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/no/state_of_css.yml b/no/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/no/state_of_css.yml +++ b/no/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 7d501a64866fc96fcf80fa0580f915d2aee27a41 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:36 +0900 Subject: [PATCH 1611/1932] New translations state_of_css.yml (Polish) --- pl/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/pl/state_of_css.yml b/pl/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/pl/state_of_css.yml +++ b/pl/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 3148fe53619f84f1cb005c18d307b2867e65bd98 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:37 +0900 Subject: [PATCH 1612/1932] New translations state_of_css.yml (Russian) --- ru/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/ru/state_of_css.yml b/ru/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/ru/state_of_css.yml +++ b/ru/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 7f81d8a6309a95e18355352408488e9baa96bc40 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:38 +0900 Subject: [PATCH 1613/1932] New translations state_of_css.yml (Serbian (Cyrillic)) --- sr/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/sr/state_of_css.yml b/sr/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/sr/state_of_css.yml +++ b/sr/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 34b015501a3fe8b6ac06f8da732615d775ef0fc2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:39 +0900 Subject: [PATCH 1614/1932] New translations state_of_css.yml (Swedish) --- sv/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/sv/state_of_css.yml b/sv/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/sv/state_of_css.yml +++ b/sv/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From c2429c24583654df1531d97bff6c9d5ffc7b97b7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:40 +0900 Subject: [PATCH 1615/1932] New translations state_of_css.yml (Turkish) --- tr/state_of_css.yml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/tr/state_of_css.yml b/tr/state_of_css.yml index adf8e76b721..64781919e20 100644 --- a/tr/state_of_css.yml +++ b/tr/state_of_css.yml @@ -139,6 +139,12 @@ translations: - key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? + - + key: sections.usage.title + t: Usage + - + key: sections.usage.description + t: How you use CSS. - ########################################################################### #Options @@ -866,6 +872,12 @@ translations: - key: environments.form_factors.description t: Which form factors or environments do you test on? + - + key: environments.form_factors.others + t: Other Testing Environments + - + key: environments.form_factors.others.description + t: Other form factors or environments you usually test on. - key: environments.accessibility_features t: Accessibility Features @@ -876,7 +888,7 @@ translations: key: environments.accessibility_features.others t: Other Accessibility Features - - key: environments.accessibility_features.others + key: environments.accessibility_features.others.description t: Other accessibility features you usually implement - key: environments.css_for_print @@ -979,10 +991,10 @@ translations: key: opinions_others.currently_missing_from_css.others t: Other Missing Features - - key: opinions_others.currently_missing_from_css.others.note - t: > - These results were normalized based on the contents of a freeform field. To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). - - + #- key: opinions_others.currently_missing_from_css.others.note + #t: > + #These results were normalized based on the contents of a freeform field. + #To view the raw, unprocessed responses check out [whatsmissingfromcss.com](http://whatsmissingfromcss.com/). key: opinions.sum_up_one_word_css t: CSS in one word - @@ -1032,8 +1044,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_css t: First Steps With CSS - - key: resources.first_steps.description + key: resources.first_steps_css.description t: When first starting out, how did you initially learn CSS? From 3d29471c0e07b03f0bbbd5cf63564895fcaa1a60 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:41 +0900 Subject: [PATCH 1616/1932] New translations state_of_js.yml (Greek) --- el/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/el/state_of_js.yml b/el/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/el/state_of_js.yml +++ b/el/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From b52d7e21465f44a948716fe5f3637e0af0559a3d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:42 +0900 Subject: [PATCH 1617/1932] New translations common.yml (Finnish) --- fi/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi/common.yml b/fi/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 873b871a85070ebd77686b3c5d337d488c23ca3a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:43 +0900 Subject: [PATCH 1618/1932] New translations common.yml (Chinese Simplified) --- zh/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/common.yml b/zh/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 29d628ad78416a2bf5881929d0c25da8441560b8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:44 +0900 Subject: [PATCH 1619/1932] New translations state_of_js.yml (Serbian (Cyrillic)) --- sr/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sr/state_of_js.yml b/sr/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/sr/state_of_js.yml +++ b/sr/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 2432cd75b9d221aa7ea3c2f1a76faabff8ef645d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:45 +0900 Subject: [PATCH 1620/1932] New translations common.yml (Swedish) --- sv/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sv/common.yml b/sv/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From bff2c19b929f2996dd461aae8f4d9cbc1e8ab9e4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:46 +0900 Subject: [PATCH 1621/1932] New translations state_of_js.yml (Swedish) --- sv/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sv/state_of_js.yml b/sv/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/sv/state_of_js.yml +++ b/sv/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 1e599c66f2a59440a35482ff48173b8ba1f82261 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:47 +0900 Subject: [PATCH 1622/1932] New translations common.yml (Turkish) --- tr/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/common.yml b/tr/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 7b06168dafe034399cc82c052ab2b353bbe7d5ad Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:48 +0900 Subject: [PATCH 1623/1932] New translations state_of_js.yml (Turkish) --- tr/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tr/state_of_js.yml b/tr/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/tr/state_of_js.yml +++ b/tr/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From dfefa21176f8015ea8abf8f8a17f5947f17443e2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:49 +0900 Subject: [PATCH 1624/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/uk/common.yml b/uk/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 2a0c74b3a65962fc38a18c4d641e54a52ccdc79c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:50 +0900 Subject: [PATCH 1625/1932] New translations state_of_js.yml (Ukrainian) --- uk/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/uk/state_of_js.yml b/uk/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/uk/state_of_js.yml +++ b/uk/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From cd2f0d1e56b030a0a419bad70d31b03f189fb8dc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:51 +0900 Subject: [PATCH 1626/1932] New translations state_of_js.yml (Chinese Simplified) --- zh/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh/state_of_js.yml b/zh/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/zh/state_of_js.yml +++ b/zh/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 4ee364c99b618265e6a0f2e4275a8a859e3d546b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:52 +0900 Subject: [PATCH 1627/1932] New translations state_of_js.yml (Russian) --- ru/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ru/state_of_js.yml b/ru/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/ru/state_of_js.yml +++ b/ru/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 2217312d98455f18c6debfa7cd4be74e52457d75 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:55 +0900 Subject: [PATCH 1628/1932] New translations common.yml (English) --- en/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/common.yml b/en/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/en/common.yml +++ b/en/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 636b80f195f5c356e834ec0606010c76c722fbcc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:56 +0900 Subject: [PATCH 1629/1932] New translations state_of_js.yml (English) --- en/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/state_of_js.yml b/en/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/en/state_of_js.yml +++ b/en/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 8d505b66e501e8d7fba1f5ec8bdde6e4dd392459 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:57 +0900 Subject: [PATCH 1630/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vi/common.yml b/vi/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 297cd15eb78845830f21f9b146a64670ab2bacee Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:58 +0900 Subject: [PATCH 1631/1932] New translations state_of_js.yml (Vietnamese) --- vi/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/vi/state_of_js.yml b/vi/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/vi/state_of_js.yml +++ b/vi/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 9bae8cf7315c9cb53b31bb0420debd35f330f06f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:18:59 +0900 Subject: [PATCH 1632/1932] New translations common.yml (Portuguese, Brazilian) --- pt/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pt/common.yml b/pt/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 5e0241b8bec360c820ca768ccaa84365b6a42e12 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:00 +0900 Subject: [PATCH 1633/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sr/common.yml b/sr/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 7761e6b85dce9510e63aaa4bc409d5499dac9909 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:01 +0900 Subject: [PATCH 1634/1932] New translations common.yml (Russian) --- ru/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ru/common.yml b/ru/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 2d6fe8ddf82bd0ad785efe97e21011dc271cf90e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:02 +0900 Subject: [PATCH 1635/1932] New translations state_of_js.yml (Finnish) --- fi/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fi/state_of_js.yml b/fi/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/fi/state_of_js.yml +++ b/fi/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 076109c87794150b8c53a0d3b4398c2c4772bef7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:03 +0900 Subject: [PATCH 1636/1932] New translations state_of_js.yml (Japanese) --- ja/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ja/state_of_js.yml b/ja/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/ja/state_of_js.yml +++ b/ja/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 8aa281db607d01ea6d0ffad114babdb4cbbd42be Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:04 +0900 Subject: [PATCH 1637/1932] New translations common.yml (Hebrew) --- he/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/he/common.yml b/he/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/he/common.yml +++ b/he/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 83825e6e0034a5a6cf7547fe4289caabe279fcda Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:05 +0900 Subject: [PATCH 1638/1932] New translations state_of_js.yml (Hebrew) --- he/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/he/state_of_js.yml b/he/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/he/state_of_js.yml +++ b/he/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 39dd92fe194a872bd1045e4377d5f6b39fc4eceb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:06 +0900 Subject: [PATCH 1639/1932] New translations common.yml (Hungarian) --- hu/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hu/common.yml b/hu/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 12ba1cb877d4c2726bd6256747e44ed46eccd9a6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:07 +0900 Subject: [PATCH 1640/1932] New translations state_of_js.yml (Hungarian) --- hu/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hu/state_of_js.yml b/hu/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/hu/state_of_js.yml +++ b/hu/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 0e7767e361542fe92ad69d8a97e5465d0466582c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:08 +0900 Subject: [PATCH 1641/1932] New translations common.yml (Italian) --- it/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/it/common.yml b/it/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/it/common.yml +++ b/it/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 1b5af54ba2c3174f6c1195bebfe0f0a74e966467 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:09 +0900 Subject: [PATCH 1642/1932] New translations state_of_js.yml (Italian) --- it/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/it/state_of_js.yml b/it/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/it/state_of_js.yml +++ b/it/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 850661d9157308618e8460c51b9a0fd1d0854a76 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:10 +0900 Subject: [PATCH 1643/1932] New translations common.yml (Japanese) --- ja/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/common.yml b/ja/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 1ba47a20550dd8f2f225863a76604aecd60947fa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:11 +0900 Subject: [PATCH 1644/1932] New translations common.yml (Korean) --- ko/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ko/common.yml b/ko/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From 3dc137cb4c5b351fa56284536e81d318bef6e366 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:12 +0900 Subject: [PATCH 1645/1932] New translations state_of_js.yml (Portuguese) --- pt/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pt/state_of_js.yml b/pt/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/pt/state_of_js.yml +++ b/pt/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 73fc41b033def8715299b9c996c29d6924b36846 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:13 +0900 Subject: [PATCH 1646/1932] New translations state_of_js.yml (Korean) --- ko/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ko/state_of_js.yml b/ko/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/ko/state_of_js.yml +++ b/ko/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 9a4e89e88d6de2590eb8123624527141c53b8a4b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:14 +0900 Subject: [PATCH 1647/1932] New translations common.yml (Dutch) --- nl/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nl/common.yml b/nl/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From e16da76f7f1e3eac20a3d999fc59f9f3fb9d47aa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:15 +0900 Subject: [PATCH 1648/1932] New translations state_of_js.yml (Dutch) --- nl/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nl/state_of_js.yml b/nl/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/nl/state_of_js.yml +++ b/nl/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From d976ae0b19274b301f4974f78e924708fb4e9af2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:17 +0900 Subject: [PATCH 1649/1932] New translations common.yml (Norwegian) --- no/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/no/common.yml b/no/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/no/common.yml +++ b/no/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From fa43edc36b558aa3d45b4d46da49b12456d74789 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:18 +0900 Subject: [PATCH 1650/1932] New translations state_of_js.yml (Norwegian) --- no/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/no/state_of_js.yml b/no/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/no/state_of_js.yml +++ b/no/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From 9567bb95386c22887cd1f48c43c847a36022ef81 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:19 +0900 Subject: [PATCH 1651/1932] New translations common.yml (Polish) --- pl/common.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pl/common.yml b/pl/common.yml index cbea1b4487e..73eb6e18678 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -1385,7 +1385,7 @@ translations: ########################################################################### #Resources ########################################################################### - #learning method + #first steps key: resources.first_steps t: First Learning Methods - From ff19182c90fa70d85001f92ae91e7add7820c287 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 03:19:20 +0900 Subject: [PATCH 1652/1932] New translations state_of_js.yml (Polish) --- pl/state_of_js.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pl/state_of_js.yml b/pl/state_of_js.yml index f11bed31b95..5d8f08df6c6 100644 --- a/pl/state_of_js.yml +++ b/pl/state_of_js.yml @@ -585,8 +585,8 @@ translations: ########################################################################### #Resources ########################################################################### - key: resources.first_steps + key: resources.first_steps_js t: First Steps With JavaScript - - key: resources.first_steps.description + key: resources.first_steps_js.description t: When first starting out, how did you initially learn JavaScript? From e879bd2f3281c353e5a8b36ff065de598341e5fc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:30 +0900 Subject: [PATCH 1653/1932] New translations state_of_css.yml (Romanian) --- ro/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ro/state_of_css.yml b/ro/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/ro/state_of_css.yml +++ b/ro/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 40ad06f0ec795906cb7b60c447235d91edbd4454 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:31 +0900 Subject: [PATCH 1654/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 9a6be250e1c137efa39961eacb03381a2101bcac Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:32 +0900 Subject: [PATCH 1655/1932] New translations state_of_css.yml (Vietnamese) --- vi/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/vi/state_of_css.yml b/vi/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/vi/state_of_css.yml +++ b/vi/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From ec11f8ac0ff44c936a6d04a10944b15d1eed7ab6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:33 +0900 Subject: [PATCH 1656/1932] New translations state_of_css.yml (Portuguese, Brazilian) --- pt/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pt/state_of_css.yml b/pt/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/pt/state_of_css.yml +++ b/pt/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From ef57403564c6957995f5637bc95c51528a93a093 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:34 +0900 Subject: [PATCH 1657/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 9bc3e511f024cf06b8ed7c5b67a7d43804a61211 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:35 +0900 Subject: [PATCH 1658/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 1133f6ce03fb29eade4ac68799d1a1731f071d5f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:36 +0900 Subject: [PATCH 1659/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 910da511fe548034c7ba3271069126defdfc0ff4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:37 +0900 Subject: [PATCH 1660/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 36137edb008eb273c5d2e5bf35dde6d8751ae1b3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:38 +0900 Subject: [PATCH 1661/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 81f01e2ed43dc09a6a167d235bc0f5246c29ca10 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:39 +0900 Subject: [PATCH 1662/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 617afaba7d9569e44e9196be837385e9d8dd8569 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:40 +0900 Subject: [PATCH 1663/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From ce5b610be4793c0c78fcfc66c7a9e2796712be73 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:41 +0900 Subject: [PATCH 1664/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 695174f1bf882b20b361975435ebe440c57dc2c2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:42 +0900 Subject: [PATCH 1665/1932] New translations state_of_css.yml (Chinese Traditional) --- zh/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/zh/state_of_css.yml b/zh/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/zh/state_of_css.yml +++ b/zh/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 205ac42d570175952c4a8d6fe4c32ccbe8639628 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:43 +0900 Subject: [PATCH 1666/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 2c9ac54e166bdd1e1385d276c9c24566c78931f9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:43 +0900 Subject: [PATCH 1667/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 09887e092bdda360105efd454e26f39826f56ed5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:44 +0900 Subject: [PATCH 1668/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From c8b5b355abaafd50f9b01dc74352ebed03ebedfe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:45 +0900 Subject: [PATCH 1669/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 62f066bea587bd7a784e00d1d967f32e037746d2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:46 +0900 Subject: [PATCH 1670/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From a86e22ca5b28553208ba202864553077b6424c69 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:47 +0900 Subject: [PATCH 1671/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 044ebf051b9f1c241eade5cf8638bf1d78aaad74 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:48 +0900 Subject: [PATCH 1672/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 0139d02aff4e35783a8f01d2b369f1394cdecf81 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:49 +0900 Subject: [PATCH 1673/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From deccc503377a8e071885d212a5755757fd1c48e6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:50 +0900 Subject: [PATCH 1674/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From eff70ed206a42d4ab3619935e7bd5684d1ae6c27 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:51 +0900 Subject: [PATCH 1675/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From c08133cc6d6563725c6d00e12cd3780e004c8b81 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:52 +0900 Subject: [PATCH 1676/1932] New translations state_of_css.yml (English) --- en/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/en/state_of_css.yml b/en/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/en/state_of_css.yml +++ b/en/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 7a5dbf3d0ee1a23682c61fb51793ca0eea3995fe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:54 +0900 Subject: [PATCH 1677/1932] New translations state_of_css.yml (French) --- fr/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/fr/state_of_css.yml b/fr/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/fr/state_of_css.yml +++ b/fr/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 653977ab599fb2c3bc235981f2313d6f42e373c0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:55 +0900 Subject: [PATCH 1678/1932] New translations state_of_css.yml (Hungarian) --- hu/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/hu/state_of_css.yml b/hu/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/hu/state_of_css.yml +++ b/hu/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 94dcb79d7f059405b7023df24e51fd9d43ee1f9d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:56 +0900 Subject: [PATCH 1679/1932] New translations state_of_css.yml (Spanish) --- es/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/es/state_of_css.yml b/es/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/es/state_of_css.yml +++ b/es/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 29dc7589a061f18c471be1b883edaad3734352a5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:57 +0900 Subject: [PATCH 1680/1932] New translations state_of_css.yml (Afrikaans) --- af/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/af/state_of_css.yml b/af/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/af/state_of_css.yml +++ b/af/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 2897e1a859b70a81e996fba116fcdf868461fe83 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:58 +0900 Subject: [PATCH 1681/1932] New translations state_of_css.yml (Arabic) --- ar/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ar/state_of_css.yml b/ar/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/ar/state_of_css.yml +++ b/ar/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 0312e14588a50d18366e2a21c4334ca3b7d69cb1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:15:59 +0900 Subject: [PATCH 1682/1932] New translations state_of_css.yml (Catalan) --- ca/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ca/state_of_css.yml b/ca/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/ca/state_of_css.yml +++ b/ca/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 7c5f4e8e151c39da297ccd889ffc1ec097e5be72 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:00 +0900 Subject: [PATCH 1683/1932] New translations state_of_css.yml (Czech) --- cs/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/cs/state_of_css.yml b/cs/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/cs/state_of_css.yml +++ b/cs/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From de5a1162cb68bf4adf64edca00d0802f37c262ac Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:02 +0900 Subject: [PATCH 1684/1932] New translations state_of_css.yml (Danish) --- da/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/da/state_of_css.yml b/da/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/da/state_of_css.yml +++ b/da/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 210bf67790b733cb70a35017820cb25ccb7e6345 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:03 +0900 Subject: [PATCH 1685/1932] New translations state_of_css.yml (German) --- de/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/de/state_of_css.yml b/de/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/de/state_of_css.yml +++ b/de/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 074d0911fb8817265821b792593883500aefe697 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:04 +0900 Subject: [PATCH 1686/1932] New translations state_of_css.yml (Greek) --- el/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/el/state_of_css.yml b/el/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/el/state_of_css.yml +++ b/el/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 61251549d902cee330c82c22177892c309e9ca9f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:05 +0900 Subject: [PATCH 1687/1932] New translations state_of_css.yml (Finnish) --- fi/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/fi/state_of_css.yml b/fi/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/fi/state_of_css.yml +++ b/fi/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 391674bd876f0fb8686bd3b613134ae803530ada Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:06 +0900 Subject: [PATCH 1688/1932] New translations state_of_css.yml (Hebrew) --- he/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/he/state_of_css.yml b/he/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/he/state_of_css.yml +++ b/he/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 4ed4b6a93af805fbd599bfd991f6044e4c710be4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:07 +0900 Subject: [PATCH 1689/1932] New translations state_of_css.yml (Italian) --- it/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/it/state_of_css.yml b/it/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/it/state_of_css.yml +++ b/it/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 95725deb6713d9894daad99127f8ad22db0d4a7c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:08 +0900 Subject: [PATCH 1690/1932] New translations state_of_css.yml (Ukrainian) --- uk/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/uk/state_of_css.yml b/uk/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/uk/state_of_css.yml +++ b/uk/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 4e92e746440eaef3a7b1ac695d1e98b57159c8d8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:09 +0900 Subject: [PATCH 1691/1932] New translations state_of_css.yml (Japanese) --- ja/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ja/state_of_css.yml b/ja/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/ja/state_of_css.yml +++ b/ja/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 63b1d69c4cb71bf8496999c5a0d8574efd178203 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:10 +0900 Subject: [PATCH 1692/1932] New translations state_of_css.yml (Korean) --- ko/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ko/state_of_css.yml b/ko/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/ko/state_of_css.yml +++ b/ko/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From d174ce241a1ffae78b2edefa7b43ff835bab0f86 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:11 +0900 Subject: [PATCH 1693/1932] New translations state_of_css.yml (Dutch) --- nl/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/nl/state_of_css.yml b/nl/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/nl/state_of_css.yml +++ b/nl/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 64696ca07db9c88afc91efe36061f9fd59df9111 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:12 +0900 Subject: [PATCH 1694/1932] New translations state_of_css.yml (Norwegian) --- no/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/no/state_of_css.yml b/no/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/no/state_of_css.yml +++ b/no/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From b8c26edaa740434539fd9d90ee964453c4abd896 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:13 +0900 Subject: [PATCH 1695/1932] New translations state_of_css.yml (Polish) --- pl/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pl/state_of_css.yml b/pl/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/pl/state_of_css.yml +++ b/pl/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 3157e5be292f201aad3ccbde8a5be7ef8a2ab198 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:15 +0900 Subject: [PATCH 1696/1932] New translations state_of_css.yml (Russian) --- ru/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ru/state_of_css.yml b/ru/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/ru/state_of_css.yml +++ b/ru/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 02e4cda59858b01d6b8b63b9e54914f5a4951ea7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:16 +0900 Subject: [PATCH 1697/1932] New translations state_of_css.yml (Serbian (Cyrillic)) --- sr/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sr/state_of_css.yml b/sr/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/sr/state_of_css.yml +++ b/sr/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 69c4b6cab12ea28376eb4056ae860c69e71db703 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:17 +0900 Subject: [PATCH 1698/1932] New translations state_of_css.yml (Swedish) --- sv/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sv/state_of_css.yml b/sv/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/sv/state_of_css.yml +++ b/sv/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From a9642c212adef56b9fa5dc19161ee357ab1d6bd9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:18 +0900 Subject: [PATCH 1699/1932] New translations state_of_css.yml (Turkish) --- tr/state_of_css.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tr/state_of_css.yml b/tr/state_of_css.yml index 64781919e20..bde402ac738 100644 --- a/tr/state_of_css.yml +++ b/tr/state_of_css.yml @@ -140,10 +140,10 @@ translations: key: sections.environments.description t: Which environments and accessibility concerns do you consider when writing CSS? - - key: sections.usage.title - t: Usage + key: sections.usage_css.title + t: CSS Usage - - key: sections.usage.description + key: sections.usage_css.description t: How you use CSS. - ########################################################################### From 42c6d9ec5a2ba78c32f91e8c314cee7487cef512 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:19 +0900 Subject: [PATCH 1700/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From bee80b9b75f7aa227929ace0944f172536c98e81 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:20 +0900 Subject: [PATCH 1701/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 2b78fecbc95fe361525c52151f2b40065f38e7a9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:21 +0900 Subject: [PATCH 1702/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From d065138cf49051fb1de704c119e6d0543c73347d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:21 +0900 Subject: [PATCH 1703/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 822e24c0c32843b11f8f631e9468446bdb87c84c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:22 +0900 Subject: [PATCH 1704/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From f3d37f9dee152ee14abe6e9b5b2ea905a5ef3306 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:23 +0900 Subject: [PATCH 1705/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 71946e69129c794b51f64e39d23a227d1127834b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:24 +0900 Subject: [PATCH 1706/1932] New translations state_of_graphql.yml (Chinese Simplified) --- zh/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From b6bc3b17ba3f7596926924338badcd7d2ac65bbb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:26 +0900 Subject: [PATCH 1707/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From 2135c13335fae174e99b8e7fb3343ae596705a5b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Mon, 18 Jul 2022 04:16:27 +0900 Subject: [PATCH 1708/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index ae1ab35b6af..966b907e135 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -89,10 +89,10 @@ translations: key: sections.schema_builders.description t: Libraries and utilities that help you build all or part of your GraphQL schema. - - key: sections.usage.title + key: sections.usage_graphql.title t: GraphQL Usage - - key: sections.usage.description + key: sections.usage_graphql.description t: How you use GraphQL. - ########################################################################### From c43d1afbb995b152aa8fe5b2a5be46a098461d57 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:38:50 +0900 Subject: [PATCH 1709/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From a1e1908aa672016e1145b0da56b2e46a1e3c33d3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:38:52 +0900 Subject: [PATCH 1710/1932] New translations results.yml (Danish) --- da/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/da/results.yml b/da/results.yml index 552cbddd626..83e16febc7e 100644 --- a/da/results.yml +++ b/da/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From f13ad2bd8b4aea8ccb1063d8350d035a48f5dd3a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:38:53 +0900 Subject: [PATCH 1711/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From e033a34b5c31b936853eb146fd26afecfad56e65 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:38:54 +0900 Subject: [PATCH 1712/1932] New translations state_of_graphql.yml (Portuguese, Brazilian) --- pt/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From ce6db2d0c47737e70760131d9382de1998876509 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:38:56 +0900 Subject: [PATCH 1713/1932] New translations results.yml (Romanian) --- ro/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ro/results.yml b/ro/results.yml index 552cbddd626..83e16febc7e 100644 --- a/ro/results.yml +++ b/ro/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 39dc24f7046841f22d020faf12a94075811f2ff8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:38:57 +0900 Subject: [PATCH 1714/1932] New translations results.yml (French) --- fr/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fr/results.yml b/fr/results.yml index 552cbddd626..83e16febc7e 100644 --- a/fr/results.yml +++ b/fr/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 2ac56607380c9a1035e9295be0d26bdd1791858a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:38:58 +0900 Subject: [PATCH 1715/1932] New translations results.yml (Spanish) --- es/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/es/results.yml b/es/results.yml index 552cbddd626..83e16febc7e 100644 --- a/es/results.yml +++ b/es/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From b5dd6652dcd3919d398bd5adb02042ffff6ed76f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:38:59 +0900 Subject: [PATCH 1716/1932] New translations results.yml (Afrikaans) --- af/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/af/results.yml b/af/results.yml index 552cbddd626..83e16febc7e 100644 --- a/af/results.yml +++ b/af/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 695a8c9a2c94d9b4984af2b4f4d71fab3048c23a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:01 +0900 Subject: [PATCH 1717/1932] New translations results.yml (Arabic) --- ar/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ar/results.yml b/ar/results.yml index 552cbddd626..83e16febc7e 100644 --- a/ar/results.yml +++ b/ar/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 7eef029c378181d31b532dad53ebb11fbb8f9dd2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:02 +0900 Subject: [PATCH 1718/1932] New translations results.yml (Catalan) --- ca/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ca/results.yml b/ca/results.yml index 552cbddd626..83e16febc7e 100644 --- a/ca/results.yml +++ b/ca/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 32d124473e608f6030fb0e80e5609f57dc970707 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:03 +0900 Subject: [PATCH 1719/1932] New translations results.yml (Czech) --- cs/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/cs/results.yml b/cs/results.yml index 552cbddd626..83e16febc7e 100644 --- a/cs/results.yml +++ b/cs/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 6ede06fa8c8bf358db0d1a0d66666a95e4281115 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:05 +0900 Subject: [PATCH 1720/1932] New translations results.yml (German) --- de/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/de/results.yml b/de/results.yml index 552cbddd626..83e16febc7e 100644 --- a/de/results.yml +++ b/de/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From ee723403407b8214cac3033a9ed0e5276b36cdbc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:07 +0900 Subject: [PATCH 1721/1932] New translations state_of_graphql.yml (Chinese Traditional) --- zh/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From ba74ca37bb31a83113f444457877ba93d2485e69 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:08 +0900 Subject: [PATCH 1722/1932] New translations results.yml (Greek) --- el/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/el/results.yml b/el/results.yml index 552cbddd626..83e16febc7e 100644 --- a/el/results.yml +++ b/el/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From f3051bdd2b9f4b9d272ed69618a0893110aba0b7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:09 +0900 Subject: [PATCH 1723/1932] New translations results.yml (Finnish) --- fi/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fi/results.yml b/fi/results.yml index 552cbddd626..83e16febc7e 100644 --- a/fi/results.yml +++ b/fi/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From de31946035c1ab77435c97ce953ff39c637d3c62 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:11 +0900 Subject: [PATCH 1724/1932] New translations results.yml (Hebrew) --- he/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/he/results.yml b/he/results.yml index 552cbddd626..83e16febc7e 100644 --- a/he/results.yml +++ b/he/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From ff41804f860e4958e99657e21b82f981be72840e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:12 +0900 Subject: [PATCH 1725/1932] New translations results.yml (Hungarian) --- hu/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/hu/results.yml b/hu/results.yml index 552cbddd626..83e16febc7e 100644 --- a/hu/results.yml +++ b/hu/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 885bc0e1c5f19c89468caee6e134ff6530a59744 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:13 +0900 Subject: [PATCH 1726/1932] New translations results.yml (Italian) --- it/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/it/results.yml b/it/results.yml index 552cbddd626..83e16febc7e 100644 --- a/it/results.yml +++ b/it/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 4aa258aa395df924f65f00a9006a9285fa77ef25 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:15 +0900 Subject: [PATCH 1727/1932] New translations results.yml (Japanese) --- ja/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ja/results.yml b/ja/results.yml index 552cbddd626..83e16febc7e 100644 --- a/ja/results.yml +++ b/ja/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 256fc18c607de34896cc6ad5c98dabf6f1f3eb5d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:16 +0900 Subject: [PATCH 1728/1932] New translations results.yml (Korean) --- ko/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ko/results.yml b/ko/results.yml index 552cbddd626..83e16febc7e 100644 --- a/ko/results.yml +++ b/ko/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 54e4d1c35d3774275b1ca21352da3905dbaf3c43 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:17 +0900 Subject: [PATCH 1729/1932] New translations results.yml (Dutch) --- nl/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/nl/results.yml b/nl/results.yml index 552cbddd626..83e16febc7e 100644 --- a/nl/results.yml +++ b/nl/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From b2ef4fadc24248f0e1a0b6db4c118da7b05749f7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:18 +0900 Subject: [PATCH 1730/1932] New translations results.yml (Norwegian) --- no/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/no/results.yml b/no/results.yml index 552cbddd626..83e16febc7e 100644 --- a/no/results.yml +++ b/no/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From d27545888f9e2cd4d965fc67edf36d19d6abbc5c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:20 +0900 Subject: [PATCH 1731/1932] New translations results.yml (Polish) --- pl/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pl/results.yml b/pl/results.yml index 552cbddd626..83e16febc7e 100644 --- a/pl/results.yml +++ b/pl/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From cfe0b1f43e39a4bfa3b7b2859792010ce9ba65a2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:21 +0900 Subject: [PATCH 1732/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From eff3bc4528d6a6e09d7e7ca02d0d12f7d0296e70 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:23 +0900 Subject: [PATCH 1733/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From efa9101b6589ca4978eda216330641290b23aec9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:24 +0900 Subject: [PATCH 1734/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 83aa6086ca3b253fb262ace572ee9e966b4f983a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:25 +0900 Subject: [PATCH 1735/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 97c4937644ec8d8ae23d770909f5c6f0b01ded72 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:26 +0900 Subject: [PATCH 1736/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From a74ce5b3a5285634d247007ae1a160617a4de9b4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:28 +0900 Subject: [PATCH 1737/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From a669213a59378cdc862e1109f1994a27eb12c984 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:29 +0900 Subject: [PATCH 1738/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 2d78f7ea08d04788004ad4483c898b44d6eb5a5e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:30 +0900 Subject: [PATCH 1739/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 8e915dfbdd140b2baba8effb0ce22e580d06a951 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:31 +0900 Subject: [PATCH 1740/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From aaa0c99f45f5af57ec4fa2974d594b07098faaa8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:32 +0900 Subject: [PATCH 1741/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From b73433d84d303c256739e3782baba4eaa0ab5347 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:33 +0900 Subject: [PATCH 1742/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 8238e4937e5e1cbf428f5859d905f793bbfafb1b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:34 +0900 Subject: [PATCH 1743/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From fc7aebb01d85428d27b0757f9d1036a7237a0dea Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:36 +0900 Subject: [PATCH 1744/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 3a4aadf969d156d7d620983e4d0057bfe4f57aaa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:37 +0900 Subject: [PATCH 1745/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From b8fce08b67e45f584088346ec589a7828cd0f886 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:38 +0900 Subject: [PATCH 1746/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 534e867cafa9a03a72ade37702d09f5ca95eeac8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:40 +0900 Subject: [PATCH 1747/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From dce14bd85bcc01f5c8b56e118b177dd5359d6bd5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:41 +0900 Subject: [PATCH 1748/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From b7db0af92e3206ca11056a0933ad5b3f4ec1371f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:42 +0900 Subject: [PATCH 1749/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From c557cc9f9c91527d73c867c0ae140766e100ea0d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:43 +0900 Subject: [PATCH 1750/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 3e5d463af454059ce3a785d39cf5f8c54f10efaa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:44 +0900 Subject: [PATCH 1751/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From d7964a0a15aadc31e621b2e8cfb6ef9beca7f9b1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:47 +0900 Subject: [PATCH 1752/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 02e9fee00cd1ef607c529a67329455329578fa98 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:48 +0900 Subject: [PATCH 1753/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 64a269e9987132b5f992798c7ef72603be59c256 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:49 +0900 Subject: [PATCH 1754/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From 41ff68765323c63a52a9b943ea81760a62f7412e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:50 +0900 Subject: [PATCH 1755/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 118 ++++++++++++++++++++-------------------- 1 file changed, 59 insertions(+), 59 deletions(-) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index 966b907e135..fe66302b7f2 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -207,58 +207,58 @@ translations: ########################################################################### #Other Tools ########################################################################### - key: other_tools.server_languages + key: tools_others.server_languages t: Server Languages - - key: other_tools.server_languages.description + key: tools_others.server_languages.description t: Which language(s) do you use to write your GraphQL back-ends? - - key: other_tools.server_languages.others - t: Other server languages + key: tools_others.server_languages.others + t: Other Server Languages - - key: other_tools.combining_schemas + key: tools_others.combining_schemas t: Combining Schemas - - key: other_tools.combining_schemas.description + key: tools_others.combining_schemas.description t: Which tools do you use to combine, aggregate, or merge GraphQL schemas from different APIs? - - key: other_tools.combining_schemas.others + key: tools_others.combining_schemas.others t: Other tools for combining schemas - - key: other_tools.graphql_ides + key: tools_others.graphql_ides t: GraphQL IDEs - - key: other_tools.graphql_ides.description + key: tools_others.graphql_ides.description t: Apps and services that help you query your GraphQL API. - - key: other_tools.graphql_ides.others + key: tools_others.graphql_ides.others t: Other GraphQL IDEs - - key: other_tools.web_frameworks + key: tools_others.web_frameworks t: Web Frameworks - - key: other_tools.web_frameworks.description + key: tools_others.web_frameworks.description t: Web frameworks that you use in conjunction with GraphQL. - - key: other_tools.web_frameworks.others - t: Other web frameworks + key: tools_others.web_frameworks.others + t: Other Web Frameworks - - key: other_tools.databases + key: tools_others.databases t: Databases - - key: other_tools.databases.description + key: tools_others.databases.description t: Which databases do you use in conjunction with GraphQL? - - key: other_tools.databases.others - t: Other databases + key: tools_others.databases.others + t: Other Databases - - key: other_tools.other_tools + key: tools_others.other_tools t: Other GraphQL Tools - - key: other_tools.other_tools.description + key: tools_others.other_tools.description t: Other tools, libraries, or services you use - - key: other_tools.other_tools.others + key: tools_others.other_tools.others t: Other GraphQL tools not previously mentioned - ########################################################################### @@ -324,22 +324,22 @@ translations: key: usage.industry_sector.others t: Other Industry Sectors - - key: usage.strong_points + key: usage.graphql_strong_points t: GraphQL Strong Points - - key: usage.strong_points.description + key: usage.graphql_strong_points.description t: What are the main reasons why you enjoy using GraphQL? - - key: usage.strong_points.others + key: usage.graphql_strong_points.others t: Other GraphQL Strong Points - - key: usage.pain_points + key: usage.graphql_pain_points t: GraphQL Pain Points - - key: usage.pain_points.description + key: usage.graphql_pain_points.description t: What are your main pain points when using GraphQL? - - key: usage.pain_points.others + key: usage.graphql_pain_points.others t: Other GraphQL Pain Points - key: happiness.state_of_graphql @@ -469,100 +469,100 @@ translations: key: options.code_generation_target.client_code t: Other client-side code (e.g. React hooks) - - key: options.strong_points.avoiding_overfetching + key: options.graphql_strong_points.avoiding_overfetching t: Avoiding Over-fetching - - key: options.strong_points.avoiding_overfetching.description + key: options.graphql_strong_points.avoiding_overfetching.description t: Keep API responses smaller by specifying exactly the data you need. - - key: options.strong_points.introspection + key: options.graphql_strong_points.introspection t: Introspection & API Documentation - - key: options.strong_points.introspection.description + key: options.graphql_strong_points.introspection.description t: Create self-documenting APIs that improve the developer experience. - - key: options.strong_points.tooling_ecosystem + key: options.graphql_strong_points.tooling_ecosystem t: Tooling & Ecosystem - - key: options.strong_points.tooling_ecosystem.description + key: options.graphql_strong_points.tooling_ecosystem.description t: The different tools, services, and libraries that use GraphQL. - - key: options.strong_points.type_checking + key: options.graphql_strong_points.type_checking t: Type-checking - - key: options.strong_points.type_checking.description + key: options.graphql_strong_points.type_checking.description t: Enforcing and validating types for every object in the API. - - key: options.strong_points.api_aggregation + key: options.graphql_strong_points.api_aggregation t: Combining Different APIs - - key: options.strong_points.api_aggregation.description + key: options.graphql_strong_points.api_aggregation.description t: Being able to combine together different API schemas. - - key: options.strong_points.aggregating_requests + key: options.graphql_strong_points.aggregating_requests t: Aggregating Requests - - key: options.strong_points.aggregating_requests.description + key: options.graphql_strong_points.aggregating_requests.description t: Only ever have to make a single request from the client. - - key: options.strong_points.community + key: options.graphql_strong_points.community t: Community - - key: options.strong_points.community.description + key: options.graphql_strong_points.community.description t: The people who are active in the GraphQL space. - - key: options.strong_points.fragment_colocation + key: options.graphql_strong_points.fragment_colocation t: Fragment Colocation - - key: options.strong_points.fragment_colocation.description + key: options.graphql_strong_points.fragment_colocation.description t: Being able to colocate a component's data requirements next to it. - - key: options.pain_points.performance + key: options.graphql_pain_points.performance t: Performance - - key: options.pain_points.performance.description + key: options.graphql_pain_points.performance.description t: Performance issues such as the n+1 problem. - - key: options.pain_points.security + key: options.graphql_pain_points.security t: Security - - key: options.pain_points.security.description + key: options.graphql_pain_points.security.description t: Security issues such as infinitely nested queries. - - key: options.pain_points.combining_schemas + key: options.graphql_pain_points.combining_schemas t: Combining Different Schemas - - key: options.pain_points.combining_schemas.description + key: options.graphql_pain_points.combining_schemas.description t: Being able to combine together different API schemas. - - key: options.pain_points.api_versioning + key: options.graphql_pain_points.api_versioning t: API Versioning - - key: options.pain_points.api_versioning.description + key: options.graphql_pain_points.api_versioning.description t: Handling deprecated fields and other versioning concerns. - - key: options.pain_points.file_upload + key: options.graphql_pain_points.file_upload t: File Upload - - key: options.pain_points.file_upload.description + key: options.graphql_pain_points.file_upload.description t: Being able to upload files through your GraphQL API. - - key: options.pain_points.testing + key: options.graphql_pain_points.testing t: Testing - - key: options.pain_points.testing.description + key: options.graphql_pain_points.testing.description t: Testing your GraphQL API. - - key: options.pain_points.error_handling + key: options.graphql_pain_points.error_handling t: Error Handling - - key: options.pain_points.error_handling.description + key: options.graphql_pain_points.error_handling.description t: Returning errors and managing them on the client. - - key: options.pain_points.client_side_caching + key: options.graphql_pain_points.client_side_caching t: Client-side Caching - - key: options.pain_points.client_side_caching.description + key: options.graphql_pain_points.client_side_caching.description t: Caching data on the client, updating the cache, optimistic UI, etc. - #learning methods From a6acc6b4ed5076219ec86666951e688a45741b1b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:51 +0900 Subject: [PATCH 1756/1932] New translations results.yml (Portuguese) --- pt/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pt/results.yml b/pt/results.yml index 552cbddd626..83e16febc7e 100644 --- a/pt/results.yml +++ b/pt/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 7f7ac16f1833b3b44e6cb02287dad09daccf1449 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:53 +0900 Subject: [PATCH 1757/1932] New translations results.yml (Russian) --- ru/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ru/results.yml b/ru/results.yml index 552cbddd626..83e16febc7e 100644 --- a/ru/results.yml +++ b/ru/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 8f10243272fd1b18ceaf84ecf4087c819d9af6eb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:54 +0900 Subject: [PATCH 1758/1932] New translations results.yml (Serbian (Cyrillic)) --- sr/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sr/results.yml b/sr/results.yml index 552cbddd626..83e16febc7e 100644 --- a/sr/results.yml +++ b/sr/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 0f4f7350fcb5f727471ba8e7da3edf6e56ce87f9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:55 +0900 Subject: [PATCH 1759/1932] New translations results.yml (Swedish) --- sv/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sv/results.yml b/sv/results.yml index 552cbddd626..83e16febc7e 100644 --- a/sv/results.yml +++ b/sv/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From c0145536b08a5f1b45d0c4ebd147304d44dac511 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:56 +0900 Subject: [PATCH 1760/1932] New translations results.yml (Turkish) --- tr/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tr/results.yml b/tr/results.yml index 552cbddd626..83e16febc7e 100644 --- a/tr/results.yml +++ b/tr/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From a2accc13dfdaba2715ec3bd1e148c86424e7f1b1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:58 +0900 Subject: [PATCH 1761/1932] New translations results.yml (Ukrainian) --- uk/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/uk/results.yml b/uk/results.yml index 552cbddd626..83e16febc7e 100644 --- a/uk/results.yml +++ b/uk/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 9b981ddcb170d4e96bda3cbb84f5ae218b6d70c1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:39:59 +0900 Subject: [PATCH 1762/1932] New translations results.yml (Chinese Simplified) --- zh/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/zh/results.yml b/zh/results.yml index 552cbddd626..83e16febc7e 100644 --- a/zh/results.yml +++ b/zh/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 804740b58b1e650fb8ad050eaa92fb7a359d2cf5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:40:02 +0900 Subject: [PATCH 1763/1932] New translations results.yml (English) --- en/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/en/results.yml b/en/results.yml index 552cbddd626..83e16febc7e 100644 --- a/en/results.yml +++ b/en/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 2d0f3b3c5674689c94ef29a40799a418e43651b2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Thu, 21 Jul 2022 00:40:03 +0900 Subject: [PATCH 1764/1932] New translations results.yml (Vietnamese) --- vi/results.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/vi/results.yml b/vi/results.yml index 552cbddd626..83e16febc7e 100644 --- a/vi/results.yml +++ b/vi/results.yml @@ -358,6 +358,9 @@ translations: - key: options.locale.pt-PT t: Portuguese + - + key: options.locale.pt-BR + t: Portuguese (Brazil) - key: options.locale.it-IT t: Italian From 4a7c9b8d005162152e43b5e6f9e569c302cd0c3c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:22 +0900 Subject: [PATCH 1765/1932] New translations common.yml (Romanian) --- ro/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/ro/common.yml b/ro/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/ro/common.yml +++ b/ro/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 4801095ac073f1ab78acfdfdbce9012a7243cf92 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:24 +0900 Subject: [PATCH 1766/1932] New translations state_of_js_2021_results.yml (Danish) --- da/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/da/state_of_js_2021_results.yml b/da/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/da/state_of_js_2021_results.yml +++ b/da/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From d19e5185c4655650d515de245b5d060bc7e02c64 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:25 +0900 Subject: [PATCH 1767/1932] New translations state_of_graphql.yml (Catalan) --- ca/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ca/state_of_graphql.yml b/ca/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/ca/state_of_graphql.yml +++ b/ca/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From aaa9a3b1c23d0e225e5f4ed2fcb3e1a0645ae2f5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:26 +0900 Subject: [PATCH 1768/1932] New translations common.yml (Czech) --- cs/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/cs/common.yml b/cs/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/cs/common.yml +++ b/cs/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 4554e43cdcb04f5c85f38359f6318894b123cc00 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:28 +0900 Subject: [PATCH 1769/1932] New translations homepage.yml (Romanian) --- ro/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ro/homepage.yml b/ro/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/ro/homepage.yml +++ b/ro/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 6a07c9bde31242121fb62121af19a000e428521c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:29 +0900 Subject: [PATCH 1770/1932] New translations state_of_js_2021_results.yml (Czech) --- cs/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/cs/state_of_js_2021_results.yml b/cs/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/cs/state_of_js_2021_results.yml +++ b/cs/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 3bba24362f168095669b00f724eb2b6d6e73f926 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:30 +0900 Subject: [PATCH 1771/1932] New translations state_of_graphql.yml (Czech) --- cs/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/cs/state_of_graphql.yml b/cs/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/cs/state_of_graphql.yml +++ b/cs/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 79e19714196a68b1bf1a106e6f2ef547b109da96 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:31 +0900 Subject: [PATCH 1772/1932] New translations common.yml (Danish) --- da/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/da/common.yml b/da/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/da/common.yml +++ b/da/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From fcd5093491426523e7da03a437f24dec9645258f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:33 +0900 Subject: [PATCH 1773/1932] New translations homepage.yml (Danish) --- da/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/da/homepage.yml b/da/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/da/homepage.yml +++ b/da/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 36bcf44ca57dd630b91008126513aaa0b3b7e6bb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:34 +0900 Subject: [PATCH 1774/1932] New translations state_of_graphql.yml (Danish) --- da/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/da/state_of_graphql.yml b/da/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/da/state_of_graphql.yml +++ b/da/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 1682b66311ea5d0a9354605a6b434e3c4bcaa2ea Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:35 +0900 Subject: [PATCH 1775/1932] New translations homepage.yml (Catalan) --- ca/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ca/homepage.yml b/ca/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/ca/homepage.yml +++ b/ca/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 8909499f7ac6c78ede5c216e3a53b0cfa90c7836 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:36 +0900 Subject: [PATCH 1776/1932] New translations common.yml (German) --- de/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/de/common.yml b/de/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/de/common.yml +++ b/de/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 97fa72b2aaa46257233a135073b21fb8a95b893d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:37 +0900 Subject: [PATCH 1777/1932] New translations homepage.yml (German) --- de/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/de/homepage.yml b/de/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/de/homepage.yml +++ b/de/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From a79089c2d92c04c8a0711fbf4c4105e33930ff2f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:39 +0900 Subject: [PATCH 1778/1932] New translations state_of_js_2021_results.yml (German) --- de/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/de/state_of_js_2021_results.yml b/de/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/de/state_of_js_2021_results.yml +++ b/de/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 2d17ca39b136ab3f25d0f211fb310256615f0eb9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:40 +0900 Subject: [PATCH 1779/1932] New translations state_of_graphql.yml (German) --- de/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/de/state_of_graphql.yml b/de/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/de/state_of_graphql.yml +++ b/de/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 6bf61491a5b302a35b7c760d94b082d3d2028c24 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:41 +0900 Subject: [PATCH 1780/1932] New translations common.yml (Greek) --- el/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/el/common.yml b/el/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/el/common.yml +++ b/el/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From ae6b44e53cb0b02be523d87a315cdbca4c439eb2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:43 +0900 Subject: [PATCH 1781/1932] New translations homepage.yml (Greek) --- el/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/el/homepage.yml b/el/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/el/homepage.yml +++ b/el/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 86c832f567f825d2a0d9fca79be30ae8b28ac2d7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:44 +0900 Subject: [PATCH 1782/1932] New translations state_of_js_2021_results.yml (Greek) --- el/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/el/state_of_js_2021_results.yml b/el/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/el/state_of_js_2021_results.yml +++ b/el/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 5de2edf88a98195a46e1b6fdbaee6624ef817e89 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:45 +0900 Subject: [PATCH 1783/1932] New translations state_of_graphql.yml (Greek) --- el/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/el/state_of_graphql.yml b/el/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/el/state_of_graphql.yml +++ b/el/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 1be4d05ec41e4864f344ca1886ab31d6247725f3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:46 +0900 Subject: [PATCH 1784/1932] New translations state_of_js_2021_results.yml (Catalan) --- ca/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ca/state_of_js_2021_results.yml b/ca/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/ca/state_of_js_2021_results.yml +++ b/ca/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From f381c2a1b5ff7b2719846c62321dbecb31e14b9d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:47 +0900 Subject: [PATCH 1785/1932] New translations homepage.yml (Czech) --- cs/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/cs/homepage.yml b/cs/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/cs/homepage.yml +++ b/cs/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 3dea3dd58d2fa88be6d4f2a1e5e31ec4917a3fa9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:49 +0900 Subject: [PATCH 1786/1932] New translations common.yml (Catalan) --- ca/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/ca/common.yml b/ca/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/ca/common.yml +++ b/ca/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From c10654ea2388e7bc9c5e0af7e8596077e0cc3d29 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:50 +0900 Subject: [PATCH 1787/1932] New translations homepage.yml (Spanish) --- es/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/es/homepage.yml b/es/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/es/homepage.yml +++ b/es/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 8c05dedeb603d833b17acb3ddb16d4bfec109e72 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:51 +0900 Subject: [PATCH 1788/1932] New translations state_of_js_2021_results.yml (Romanian) --- ro/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ro/state_of_js_2021_results.yml b/ro/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/ro/state_of_js_2021_results.yml +++ b/ro/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 01e734de7276e319a67bf3777ec1c31b94befdc4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:52 +0900 Subject: [PATCH 1789/1932] New translations state_of_graphql.yml (Romanian) --- ro/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ro/state_of_graphql.yml b/ro/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/ro/state_of_graphql.yml +++ b/ro/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 98a6399f6547bf3f5ff53850bb814c885e172ec2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:54 +0900 Subject: [PATCH 1790/1932] New translations common.yml (French) --- fr/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/fr/common.yml b/fr/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/fr/common.yml +++ b/fr/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From a2340d61b4d3d9d106398d1b822aa7ffc201a12d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:55 +0900 Subject: [PATCH 1791/1932] New translations homepage.yml (French) --- fr/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/fr/homepage.yml b/fr/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/fr/homepage.yml +++ b/fr/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From c5adf4727d422ae4fda784ea539dd44c6a501d68 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:56 +0900 Subject: [PATCH 1792/1932] New translations state_of_graphql.yml (Arabic) --- ar/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ar/state_of_graphql.yml b/ar/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/ar/state_of_graphql.yml +++ b/ar/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From d9b75bcda86e4230d9db753e413caab9b549c2d8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:57 +0900 Subject: [PATCH 1793/1932] New translations state_of_graphql.yml (French) --- fr/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/fr/state_of_graphql.yml b/fr/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/fr/state_of_graphql.yml +++ b/fr/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 01c77059c7fa0e5ee36441b89f6520bcd38adfa8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:26:58 +0900 Subject: [PATCH 1794/1932] New translations common.yml (Spanish) --- es/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/es/common.yml b/es/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/es/common.yml +++ b/es/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 0cbafbd4588dc084ce8eb73064d41c261e349144 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:00 +0900 Subject: [PATCH 1795/1932] New translations state_of_js_2021_results.yml (French) --- fr/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/fr/state_of_js_2021_results.yml b/fr/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/fr/state_of_js_2021_results.yml +++ b/fr/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 1029a57ecacf0b6b04a3814f2ead099d716966c3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:01 +0900 Subject: [PATCH 1796/1932] New translations state_of_js_2021_results.yml (Spanish) --- es/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/es/state_of_js_2021_results.yml b/es/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/es/state_of_js_2021_results.yml +++ b/es/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 2135971d8ada8511592189b32a85f2712cd12303 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:02 +0900 Subject: [PATCH 1797/1932] New translations common.yml (Afrikaans) --- af/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/af/common.yml b/af/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/af/common.yml +++ b/af/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 05772dc61e277ec5eec9e4b375df2e916adecb07 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:04 +0900 Subject: [PATCH 1798/1932] New translations homepage.yml (Afrikaans) --- af/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/af/homepage.yml b/af/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/af/homepage.yml +++ b/af/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 536f095e1478051b898e33cc662827d73a14f5dc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:05 +0900 Subject: [PATCH 1799/1932] New translations state_of_js_2021_results.yml (Afrikaans) --- af/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/af/state_of_js_2021_results.yml b/af/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/af/state_of_js_2021_results.yml +++ b/af/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 2707483c7aae3fd8e5b43b840096862dedd2c6dd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:06 +0900 Subject: [PATCH 1800/1932] New translations state_of_graphql.yml (Afrikaans) --- af/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/af/state_of_graphql.yml b/af/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/af/state_of_graphql.yml +++ b/af/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From abb088201dbf3b2d45fcb201287ede922a56f02a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:07 +0900 Subject: [PATCH 1801/1932] New translations common.yml (Arabic) --- ar/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/ar/common.yml b/ar/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/ar/common.yml +++ b/ar/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From b85471d2bb32a6a99b857143b0620b948db80484 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:09 +0900 Subject: [PATCH 1802/1932] New translations homepage.yml (Arabic) --- ar/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ar/homepage.yml b/ar/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/ar/homepage.yml +++ b/ar/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 63777ce40c60c3040f8b2cdd931dac4c8069ce2d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:10 +0900 Subject: [PATCH 1803/1932] New translations state_of_js_2021_results.yml (Arabic) --- ar/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ar/state_of_js_2021_results.yml b/ar/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/ar/state_of_js_2021_results.yml +++ b/ar/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 872b24efa8a498ce3b77c235c2f3d13166f3e0c0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:11 +0900 Subject: [PATCH 1804/1932] New translations state_of_graphql.yml (Spanish) --- es/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/es/state_of_graphql.yml b/es/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/es/state_of_graphql.yml +++ b/es/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 700c582eb7aec8d59142d2eddb9b58f33765d47f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:12 +0900 Subject: [PATCH 1805/1932] New translations homepage.yml (Hebrew) --- he/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/he/homepage.yml b/he/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/he/homepage.yml +++ b/he/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From b0b3453762a7e1753c1f67cfdd305ea296e637b4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:14 +0900 Subject: [PATCH 1806/1932] New translations common.yml (Hungarian) --- hu/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/hu/common.yml b/hu/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/hu/common.yml +++ b/hu/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 0db83c4a48c0ac75d8380df196949769e35d5ebe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:15 +0900 Subject: [PATCH 1807/1932] New translations state_of_graphql.yml (Hebrew) --- he/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/he/state_of_graphql.yml b/he/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/he/state_of_graphql.yml +++ b/he/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 0f9b67f8be1fdb2a3f7e6737efb1bef957c6f013 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:16 +0900 Subject: [PATCH 1808/1932] New translations state_of_js_2021_results.yml (Hebrew) --- he/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/he/state_of_js_2021_results.yml b/he/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/he/state_of_js_2021_results.yml +++ b/he/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From ea12c083c560943f9be3ee8969ab005335f5f2e2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:17 +0900 Subject: [PATCH 1809/1932] New translations common.yml (Finnish) --- fi/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/fi/common.yml b/fi/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/fi/common.yml +++ b/fi/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From e85e95bbb70ee230630c587b871d9cba96d87838 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:18 +0900 Subject: [PATCH 1810/1932] New translations common.yml (Hebrew) --- he/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/he/common.yml b/he/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/he/common.yml +++ b/he/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 62524449adfcc63a4469f41f2e01726dd9958aa6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:20 +0900 Subject: [PATCH 1811/1932] New translations state_of_graphql.yml (Finnish) --- fi/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/fi/state_of_graphql.yml b/fi/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/fi/state_of_graphql.yml +++ b/fi/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 72f641c5a72aab4d6d49511e1ad4550859e43fd1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:21 +0900 Subject: [PATCH 1812/1932] New translations state_of_js_2021_results.yml (Finnish) --- fi/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/fi/state_of_js_2021_results.yml b/fi/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/fi/state_of_js_2021_results.yml +++ b/fi/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 40557ef858e7e8609455a9e2f43e23759cec9ea4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:22 +0900 Subject: [PATCH 1813/1932] New translations homepage.yml (Finnish) --- fi/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/fi/homepage.yml b/fi/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/fi/homepage.yml +++ b/fi/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 7b14d3c3213975c57d2821bdcf3db3c3cf25ee51 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:23 +0900 Subject: [PATCH 1814/1932] New translations homepage.yml (Hungarian) --- hu/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/hu/homepage.yml b/hu/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/hu/homepage.yml +++ b/hu/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 2e881f7dc7e1076aef6f7bb3854a7c4c265b5434 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:24 +0900 Subject: [PATCH 1815/1932] New translations state_of_js_2021_results.yml (Hungarian) --- hu/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/hu/state_of_js_2021_results.yml b/hu/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/hu/state_of_js_2021_results.yml +++ b/hu/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From ebd0cf8f50feded1462d6d44962352fba7f56bd2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:26 +0900 Subject: [PATCH 1816/1932] New translations state_of_graphql.yml (Serbian (Cyrillic)) --- sr/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/sr/state_of_graphql.yml b/sr/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/sr/state_of_graphql.yml +++ b/sr/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From dc2d804e232002c609024f154f8ecf7d8a319771 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:27 +0900 Subject: [PATCH 1817/1932] New translations state_of_js_2021_results.yml (Portuguese) --- pt/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pt/state_of_js_2021_results.yml b/pt/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/pt/state_of_js_2021_results.yml +++ b/pt/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From bae868e5b4f19fcba63fb22dc2ddece4aeff3cf0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:28 +0900 Subject: [PATCH 1818/1932] New translations state_of_graphql.yml (Portuguese) --- pt/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/pt/state_of_graphql.yml b/pt/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/pt/state_of_graphql.yml +++ b/pt/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 7419aec37090a62941e62d8db05418378ac8ad52 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:29 +0900 Subject: [PATCH 1819/1932] New translations common.yml (Russian) --- ru/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/ru/common.yml b/ru/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/ru/common.yml +++ b/ru/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 3a3628f2fb5bdeb3756b41bbc8d9ab8c33be33f6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:30 +0900 Subject: [PATCH 1820/1932] New translations homepage.yml (Russian) --- ru/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ru/homepage.yml b/ru/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/ru/homepage.yml +++ b/ru/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From dd20554ffb68a963880036b3b553902c29a5c292 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:32 +0900 Subject: [PATCH 1821/1932] New translations state_of_js_2021_results.yml (Russian) --- ru/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ru/state_of_js_2021_results.yml b/ru/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/ru/state_of_js_2021_results.yml +++ b/ru/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 3ff9853e92bd734e9403cbefc2e70695018a7b25 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:33 +0900 Subject: [PATCH 1822/1932] New translations state_of_graphql.yml (Russian) --- ru/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ru/state_of_graphql.yml b/ru/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/ru/state_of_graphql.yml +++ b/ru/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From cde517222c049d1627458aed25516b43d9f526fa Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:34 +0900 Subject: [PATCH 1823/1932] New translations common.yml (Serbian (Cyrillic)) --- sr/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/sr/common.yml b/sr/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/sr/common.yml +++ b/sr/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 90b76946de33bd0b650d69fcfdcfa91483cd0eba Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:35 +0900 Subject: [PATCH 1824/1932] New translations homepage.yml (Serbian (Cyrillic)) --- sr/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sr/homepage.yml b/sr/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/sr/homepage.yml +++ b/sr/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 99d81f41dcc71ae1fce238357fc47d3bb2b15333 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:36 +0900 Subject: [PATCH 1825/1932] New translations state_of_js_2021_results.yml (Serbian (Cyrillic)) --- sr/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/sr/state_of_js_2021_results.yml b/sr/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/sr/state_of_js_2021_results.yml +++ b/sr/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From ebdb23c90525e85eb0bf1eaddd7fac37c7173baf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:38 +0900 Subject: [PATCH 1826/1932] New translations common.yml (Swedish) --- sv/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/sv/common.yml b/sv/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/sv/common.yml +++ b/sv/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 0107d4bb8004f8de984cffd0688c87946cc7d458 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:39 +0900 Subject: [PATCH 1827/1932] New translations common.yml (Portuguese) --- pt/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/pt/common.yml b/pt/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/pt/common.yml +++ b/pt/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 1053004107fc9fa6e2e6288c0477bbfa160d602d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:40 +0900 Subject: [PATCH 1828/1932] New translations homepage.yml (Swedish) --- sv/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sv/homepage.yml b/sv/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/sv/homepage.yml +++ b/sv/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From e2e970ed6dfef4440bd2391637f269dfcab2983b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:41 +0900 Subject: [PATCH 1829/1932] New translations state_of_js_2021_results.yml (Swedish) --- sv/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/sv/state_of_js_2021_results.yml b/sv/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/sv/state_of_js_2021_results.yml +++ b/sv/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From a9dae3daa2921a60ec40a125e6e26c58ee044910 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:43 +0900 Subject: [PATCH 1830/1932] New translations state_of_graphql.yml (Swedish) --- sv/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/sv/state_of_graphql.yml b/sv/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/sv/state_of_graphql.yml +++ b/sv/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From e75e385db92b0146f68a97f876468472465a671c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:44 +0900 Subject: [PATCH 1831/1932] New translations common.yml (Turkish) --- tr/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/tr/common.yml b/tr/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/tr/common.yml +++ b/tr/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 7dca74f11528bb485e9996377952aa7149271d01 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:45 +0900 Subject: [PATCH 1832/1932] New translations homepage.yml (Turkish) --- tr/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tr/homepage.yml b/tr/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/tr/homepage.yml +++ b/tr/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 88f894983a729b885b3cd49df70062ddcac254d0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:46 +0900 Subject: [PATCH 1833/1932] New translations state_of_js_2021_results.yml (Turkish) --- tr/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tr/state_of_js_2021_results.yml b/tr/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/tr/state_of_js_2021_results.yml +++ b/tr/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From e22205cf6d73830fb133a8e7220cfc6e9e81860c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:48 +0900 Subject: [PATCH 1834/1932] New translations state_of_graphql.yml (Turkish) --- tr/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/tr/state_of_graphql.yml b/tr/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/tr/state_of_graphql.yml +++ b/tr/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 6ffe116c52fc268bdc14ac4c5b222aa6a8e3e537 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:49 +0900 Subject: [PATCH 1835/1932] New translations common.yml (Ukrainian) --- uk/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/uk/common.yml b/uk/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/uk/common.yml +++ b/uk/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From e3e16a722d31c8e6aeab1e567249d2b35108eb9b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:50 +0900 Subject: [PATCH 1836/1932] New translations homepage.yml (Ukrainian) --- uk/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/uk/homepage.yml b/uk/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/uk/homepage.yml +++ b/uk/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 22ce0ac311ec12d9a8305da8954a650c3253e011 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:52 +0900 Subject: [PATCH 1837/1932] New translations state_of_js_2021_results.yml (Ukrainian) --- uk/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/uk/state_of_js_2021_results.yml b/uk/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/uk/state_of_js_2021_results.yml +++ b/uk/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 4276dd55aff0acf75d035a563edc463ace8b5aef Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:53 +0900 Subject: [PATCH 1838/1932] New translations homepage.yml (Portuguese) --- pt/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pt/homepage.yml b/pt/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/pt/homepage.yml +++ b/pt/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 705548f6917b811255de65b170967d1f061726f4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:54 +0900 Subject: [PATCH 1839/1932] New translations state_of_graphql.yml (Polish) --- pl/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/pl/state_of_graphql.yml b/pl/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/pl/state_of_graphql.yml +++ b/pl/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 8dd23531d0ac768fc51e0481bf55485a6cdbc6a8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:55 +0900 Subject: [PATCH 1840/1932] New translations state_of_graphql.yml (Hungarian) --- hu/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/hu/state_of_graphql.yml b/hu/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/hu/state_of_graphql.yml +++ b/hu/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From d5257247702866d1a2ca9aa85849af05d01e7d08 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:56 +0900 Subject: [PATCH 1841/1932] New translations state_of_js_2021_results.yml (Korean) --- ko/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ko/state_of_js_2021_results.yml b/ko/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/ko/state_of_js_2021_results.yml +++ b/ko/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 87a124734b8701bfd0db89f15bb1d22e8ac079da Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:57 +0900 Subject: [PATCH 1842/1932] New translations common.yml (Italian) --- it/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/it/common.yml b/it/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/it/common.yml +++ b/it/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From d6f7b9e744502579bbbf5a04b9359891462ff700 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:27:59 +0900 Subject: [PATCH 1843/1932] New translations homepage.yml (Italian) --- it/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/it/homepage.yml b/it/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/it/homepage.yml +++ b/it/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 069a2b255a710f0356bda6cc34da081b2ae03f94 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:00 +0900 Subject: [PATCH 1844/1932] New translations state_of_js_2021_results.yml (Italian) --- it/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/it/state_of_js_2021_results.yml b/it/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/it/state_of_js_2021_results.yml +++ b/it/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From a725012142324508cac229b6a40be8afae1b4a50 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:01 +0900 Subject: [PATCH 1845/1932] New translations state_of_graphql.yml (Italian) --- it/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/it/state_of_graphql.yml b/it/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/it/state_of_graphql.yml +++ b/it/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 2b604d83f14ebbe2997012fba963e699a1c3efb0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:03 +0900 Subject: [PATCH 1846/1932] New translations common.yml (Japanese) --- ja/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/ja/common.yml b/ja/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/ja/common.yml +++ b/ja/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From d43b79c3f8bd278184f3c47d6d1694ca64458fbf Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:04 +0900 Subject: [PATCH 1847/1932] New translations homepage.yml (Japanese) --- ja/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ja/homepage.yml b/ja/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/ja/homepage.yml +++ b/ja/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 6095bf98e9ba0438bfc7fd57ec617eb3660cfe8a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:05 +0900 Subject: [PATCH 1848/1932] New translations state_of_js_2021_results.yml (Japanese) --- ja/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ja/state_of_js_2021_results.yml b/ja/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/ja/state_of_js_2021_results.yml +++ b/ja/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 30e3de486eef0ba42841d430dfa662097c0cbb4b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:07 +0900 Subject: [PATCH 1849/1932] New translations state_of_graphql.yml (Japanese) --- ja/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ja/state_of_graphql.yml b/ja/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/ja/state_of_graphql.yml +++ b/ja/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From d500623763b32b411e07bbac4484d70c46b8c128 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:08 +0900 Subject: [PATCH 1850/1932] New translations common.yml (Korean) --- ko/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/ko/common.yml b/ko/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/ko/common.yml +++ b/ko/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 92aa49fff4a81b2e9a64bea8465807d2967f4b1d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:09 +0900 Subject: [PATCH 1851/1932] New translations homepage.yml (Korean) --- ko/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ko/homepage.yml b/ko/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/ko/homepage.yml +++ b/ko/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From f2c934cd1dbb10bb1a59f59fd70e0c4e85d72906 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:10 +0900 Subject: [PATCH 1852/1932] New translations state_of_graphql.yml (Korean) --- ko/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/ko/state_of_graphql.yml b/ko/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/ko/state_of_graphql.yml +++ b/ko/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 57abff0f19105b9ef435e2a8480d0fd8d840f70a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:12 +0900 Subject: [PATCH 1853/1932] New translations state_of_js_2021_results.yml (Polish) --- pl/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pl/state_of_js_2021_results.yml b/pl/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/pl/state_of_js_2021_results.yml +++ b/pl/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 607f8121ae14c64d2a6f614755a9691c9208f172 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:13 +0900 Subject: [PATCH 1854/1932] New translations common.yml (Dutch) --- nl/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/nl/common.yml b/nl/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/nl/common.yml +++ b/nl/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 270ade719b642c7c9f1562d424af39a2c68ee927 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:14 +0900 Subject: [PATCH 1855/1932] New translations homepage.yml (Dutch) --- nl/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/nl/homepage.yml b/nl/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/nl/homepage.yml +++ b/nl/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 6742a9af14789f214baaf162224541d25b19b1ca Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:15 +0900 Subject: [PATCH 1856/1932] New translations state_of_js_2021_results.yml (Dutch) --- nl/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/nl/state_of_js_2021_results.yml b/nl/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/nl/state_of_js_2021_results.yml +++ b/nl/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From f0b05e664914e066bf18d72085842fae9c1e87e9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:17 +0900 Subject: [PATCH 1857/1932] New translations state_of_graphql.yml (Dutch) --- nl/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/nl/state_of_graphql.yml b/nl/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/nl/state_of_graphql.yml +++ b/nl/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From b0c1ba28cb141015260f2f756c8134b81305fce6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:18 +0900 Subject: [PATCH 1858/1932] New translations common.yml (Norwegian) --- no/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/no/common.yml b/no/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/no/common.yml +++ b/no/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 47f91a3c1d7b2486735743efa48a89889b54c8c7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:19 +0900 Subject: [PATCH 1859/1932] New translations homepage.yml (Norwegian) --- no/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/no/homepage.yml b/no/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/no/homepage.yml +++ b/no/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 59cc3ef0875cf78598a5ab3a16584310e89bd39e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:21 +0900 Subject: [PATCH 1860/1932] New translations state_of_js_2021_results.yml (Norwegian) --- no/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/no/state_of_js_2021_results.yml b/no/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/no/state_of_js_2021_results.yml +++ b/no/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 0cf31815798b4f97c7ba3f514aafe20d5dfa34d4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:22 +0900 Subject: [PATCH 1861/1932] New translations state_of_graphql.yml (Norwegian) --- no/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/no/state_of_graphql.yml b/no/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/no/state_of_graphql.yml +++ b/no/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From decdcb86b57b548aa66f6d5aa73783ffa669c286 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:23 +0900 Subject: [PATCH 1862/1932] New translations common.yml (Polish) --- pl/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/pl/common.yml b/pl/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/pl/common.yml +++ b/pl/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 535d93fde3174c09ce6edecff3a07ade99e2b985 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:24 +0900 Subject: [PATCH 1863/1932] New translations homepage.yml (Polish) --- pl/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pl/homepage.yml b/pl/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/pl/homepage.yml +++ b/pl/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From ef80cb93f7aaf481bb6b5ec8abc55d40ce2d8d36 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:26 +0900 Subject: [PATCH 1864/1932] New translations state_of_graphql.yml (Ukrainian) --- uk/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/uk/state_of_graphql.yml b/uk/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/uk/state_of_graphql.yml +++ b/uk/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 94bd8820c700e9066eaaca3f4273825a5c4ab788 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:27 +0900 Subject: [PATCH 1865/1932] New translations state_of_graphql_2022.yml (Spanish) --- es/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 es/state_of_graphql_2022.yml diff --git a/es/state_of_graphql_2022.yml b/es/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/es/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 48a8439468c47ab5aa91cd54384dfe0d2281227e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:28 +0900 Subject: [PATCH 1866/1932] New translations state_of_graphql_2022.yml (Danish) --- da/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 da/state_of_graphql_2022.yml diff --git a/da/state_of_graphql_2022.yml b/da/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/da/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From b289683e003ef210ccc8f303e441835cc4f00de2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:29 +0900 Subject: [PATCH 1867/1932] New translations state_of_graphql_2022.yml (Afrikaans) --- af/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 af/state_of_graphql_2022.yml diff --git a/af/state_of_graphql_2022.yml b/af/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/af/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 766ee3832412ed03f270166cdda45ab70c295b39 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:30 +0900 Subject: [PATCH 1868/1932] New translations legacy.yml (Afrikaans) --- af/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 af/legacy.yml diff --git a/af/legacy.yml b/af/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/af/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From b5ca41c5c808a7452a19fbf57dc0d42f78a64aed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:31 +0900 Subject: [PATCH 1869/1932] New translations legacy.yml (Catalan) --- ca/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 ca/legacy.yml diff --git a/ca/legacy.yml b/ca/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/ca/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 70a709a65401b9e653f0a1cd42cb4edce8636818 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:32 +0900 Subject: [PATCH 1870/1932] New translations legacy.yml (Spanish) --- es/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 es/legacy.yml diff --git a/es/legacy.yml b/es/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/es/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From c944416cdeb2297664ac330446cf272af100a86d Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:33 +0900 Subject: [PATCH 1871/1932] New translations state_of_graphql_2022.yml (French) --- fr/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 fr/state_of_graphql_2022.yml diff --git a/fr/state_of_graphql_2022.yml b/fr/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/fr/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 9d3d4885e092292c8230d575f559cd236edb875a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:34 +0900 Subject: [PATCH 1872/1932] New translations legacy.yml (French) --- fr/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 fr/legacy.yml diff --git a/fr/legacy.yml b/fr/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/fr/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From bb78d8d8f5411a611ff3421fccb498ab0e3baaae Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:35 +0900 Subject: [PATCH 1873/1932] New translations state_of_graphql_2022.yml (Romanian) --- ro/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 ro/state_of_graphql_2022.yml diff --git a/ro/state_of_graphql_2022.yml b/ro/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/ro/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 86802485de16860da73ea3123518d75a09230060 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:36 +0900 Subject: [PATCH 1874/1932] New translations legacy.yml (Romanian) --- ro/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 ro/legacy.yml diff --git a/ro/legacy.yml b/ro/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/ro/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 128364bd00d5fa94741d5156954f35802fffa3b2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:37 +0900 Subject: [PATCH 1875/1932] New translations state_of_graphql_2022.yml (Catalan) --- ca/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 ca/state_of_graphql_2022.yml diff --git a/ca/state_of_graphql_2022.yml b/ca/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/ca/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From d300b7a1a8e1086efaa38924a77cd576c1b8a556 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:38 +0900 Subject: [PATCH 1876/1932] New translations legacy.yml (Czech) --- cs/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 cs/legacy.yml diff --git a/cs/legacy.yml b/cs/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/cs/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 4125363999dcb88325e31a4a1bc4e6ca6e898df2 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:39 +0900 Subject: [PATCH 1877/1932] New translations state_of_graphql_2022.yml (Czech) --- cs/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 cs/state_of_graphql_2022.yml diff --git a/cs/state_of_graphql_2022.yml b/cs/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/cs/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 774410e975b2f2e70eee29ea299ad096adb0f4d7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:41 +0900 Subject: [PATCH 1878/1932] New translations legacy.yml (Danish) --- da/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 da/legacy.yml diff --git a/da/legacy.yml b/da/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/da/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 39461984e8a979eb575250099c90c3675c38b5c5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:42 +0900 Subject: [PATCH 1879/1932] New translations legacy.yml (German) --- de/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 de/legacy.yml diff --git a/de/legacy.yml b/de/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/de/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 03c980790dcfe31d980051cf7127c76ea5544761 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:43 +0900 Subject: [PATCH 1880/1932] New translations state_of_graphql_2022.yml (Arabic) --- ar/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 ar/state_of_graphql_2022.yml diff --git a/ar/state_of_graphql_2022.yml b/ar/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/ar/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From abd482f3f63ca0cd389a09f81345da808f3e0ff3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:44 +0900 Subject: [PATCH 1881/1932] New translations state_of_graphql_2022.yml (German) --- de/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 de/state_of_graphql_2022.yml diff --git a/de/state_of_graphql_2022.yml b/de/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/de/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 475b8f20c9e5d4a33a10c589600995f0a119fe18 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:45 +0900 Subject: [PATCH 1882/1932] New translations legacy.yml (Greek) --- el/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 el/legacy.yml diff --git a/el/legacy.yml b/el/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/el/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From d3d27191bfe04c6830319d87796c51daa24126c0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:46 +0900 Subject: [PATCH 1883/1932] New translations legacy.yml (Arabic) --- ar/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 ar/legacy.yml diff --git a/ar/legacy.yml b/ar/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/ar/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From a542fc1b2ef10dc526b8799a6f0f286d530e1879 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:47 +0900 Subject: [PATCH 1884/1932] New translations state_of_graphql_2022.yml (Greek) --- el/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 el/state_of_graphql_2022.yml diff --git a/el/state_of_graphql_2022.yml b/el/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/el/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 6c31506cc16d8bf17172ceadd71f9e64a6be1568 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:48 +0900 Subject: [PATCH 1885/1932] New translations legacy.yml (Finnish) --- fi/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 fi/legacy.yml diff --git a/fi/legacy.yml b/fi/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/fi/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From f06ea907a26790c0e056bd2869bf0a0cc0f56667 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:49 +0900 Subject: [PATCH 1886/1932] New translations state_of_graphql_2022.yml (Finnish) --- fi/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 fi/state_of_graphql_2022.yml diff --git a/fi/state_of_graphql_2022.yml b/fi/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/fi/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 2adbb0b56c10baced38859cd87d4246e860d53e3 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:51 +0900 Subject: [PATCH 1887/1932] New translations legacy.yml (Hebrew) --- he/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 he/legacy.yml diff --git a/he/legacy.yml b/he/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/he/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From f652914bf084a016dfc92c1b88e0a32adeb12df4 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:51 +0900 Subject: [PATCH 1888/1932] New translations state_of_graphql_2022.yml (Hebrew) --- he/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 he/state_of_graphql_2022.yml diff --git a/he/state_of_graphql_2022.yml b/he/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/he/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 5464fa6b41042643d9795c6bebce6f25c81dd239 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:53 +0900 Subject: [PATCH 1889/1932] New translations legacy.yml (Hungarian) --- hu/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 hu/legacy.yml diff --git a/hu/legacy.yml b/hu/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/hu/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From b7dec29107206c0f6df065a0403865492a2c76b6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:54 +0900 Subject: [PATCH 1890/1932] New translations state_of_graphql_2022.yml (Hungarian) --- hu/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 hu/state_of_graphql_2022.yml diff --git a/hu/state_of_graphql_2022.yml b/hu/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/hu/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 7e32ed0b59b0c5dd66397ee819e011370f34a909 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:55 +0900 Subject: [PATCH 1891/1932] New translations legacy.yml (Italian) --- it/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 it/legacy.yml diff --git a/it/legacy.yml b/it/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/it/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From cf6cf10c4043fe4d8bab3cf7af431847db01d7c6 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:56 +0900 Subject: [PATCH 1892/1932] New translations state_of_graphql_2022.yml (Italian) --- it/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 it/state_of_graphql_2022.yml diff --git a/it/state_of_graphql_2022.yml b/it/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/it/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 9ccc57d5cca5d5ab9fd0cbfd055394314b7364ed Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:58 +0900 Subject: [PATCH 1893/1932] New translations legacy.yml (Japanese) --- ja/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 ja/legacy.yml diff --git a/ja/legacy.yml b/ja/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/ja/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 9bb38813ee7d84ca9a7cf13649c16837038cebdc Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:28:59 +0900 Subject: [PATCH 1894/1932] New translations common.yml (Chinese Simplified) --- zh/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/zh/common.yml b/zh/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/zh/common.yml +++ b/zh/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 72c9a5272ebab05d75ad7c7f35896d28d1b10288 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:01 +0900 Subject: [PATCH 1895/1932] New translations homepage.yml (Chinese Simplified) --- zh/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/zh/homepage.yml b/zh/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/zh/homepage.yml +++ b/zh/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 6074a6e105b4fccdedb74062f706c8ed44f931fd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:02 +0900 Subject: [PATCH 1896/1932] New translations homepage.yml (English) --- en/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/en/homepage.yml b/en/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/en/homepage.yml +++ b/en/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From e9ff34d9af96ab6e3625d481e337deef16850a62 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:03 +0900 Subject: [PATCH 1897/1932] New translations state_of_js_2021_results.yml (Chinese Simplified) --- zh/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/zh/state_of_js_2021_results.yml b/zh/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/zh/state_of_js_2021_results.yml +++ b/zh/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From a313953d249f0adbbd569ca8456220e4365c951a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:05 +0900 Subject: [PATCH 1898/1932] New translations state_of_graphql.yml (Chinese Simplified) --- zh/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/zh/state_of_graphql.yml b/zh/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/zh/state_of_graphql.yml +++ b/zh/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From d969988e93adabcd864fb905bb8fc85c99b7d787 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:09 +0900 Subject: [PATCH 1899/1932] New translations common.yml (English) --- en/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/en/common.yml b/en/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/en/common.yml +++ b/en/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 9e68acdc09fcc1dcb1767e027a9b57740eb0c03f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:11 +0900 Subject: [PATCH 1900/1932] New translations state_of_js_2021_results.yml (English) --- en/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/en/state_of_js_2021_results.yml b/en/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/en/state_of_js_2021_results.yml +++ b/en/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From 7f4e8ef1c5ffe6f4393148d52a7196ef0c604eb7 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:13 +0900 Subject: [PATCH 1901/1932] New translations state_of_graphql.yml (English) --- en/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/en/state_of_graphql.yml b/en/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/en/state_of_graphql.yml +++ b/en/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From b9935c492dd1c25defb520dc772e341c6a41a489 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:14 +0900 Subject: [PATCH 1902/1932] New translations common.yml (Vietnamese) --- vi/common.yml | 83 +++++---------------------------------------------- 1 file changed, 7 insertions(+), 76 deletions(-) diff --git a/vi/common.yml b/vi/common.yml index 73eb6e18678..d62c146f1b6 100644 --- a/vi/common.yml +++ b/vi/common.yml @@ -615,82 +615,6 @@ translations: - key: options.yearly_salary.range_more_than_200.short t: '>$200k' - - - #job titles - key: options.job_title.cto - t: CTO - - - key: options.job_title.front_end_developer - t: Front End Developer/Engineer - - - key: options.job_title.back_end_developer - t: Back End Developer/Engineer - - - key: options.job_title.full_stack_developer - t: Full Stack Developer/Engineer - - - key: options.job_title.web_developer - t: Web Developer - - - key: options.job_title.web_designer - t: Web Designer - - - key: options.job_title.ux_designer - t: UX Designer - - - key: options.job_title.ui_designer - t: UI Designer - - - key: options.job_title.back_end_dev - t: Back-end Developer/Engineer - - - #JavaScript proficiency - key: options.javascript_proficiency.0 - t: Not able to write any JavaScript - - - key: options.javascript_proficiency.1 - t: Writing short, simple JavaScript or jQuery statements - - - key: options.javascript_proficiency.2 - t: Working on existing front-end codebases using modern frameworks (React, Vue, etc.) - - - key: options.javascript_proficiency.3 - t: Architecturing entire front-end codebases from scratch - - - key: options.javascript_proficiency.4 - t: Handling advanced front-end patterns (state management, data loading, etc.) - - - #CSS proficiency - key: options.css_proficiency.0 - t: Virtually no knowledge of CSS - - - key: options.css_proficiency.1 - t: Using CSS frameworks and tweaking existing styles - - - key: options.css_proficiency.2 - t: Knowing specificity rules, being able to create layouts - - - key: options.css_proficiency.3 - t: Mastering animations, interactions, transitions, etc. - - - key: options.css_proficiency.4 - t: Able to style an entire front-end from scratch following a consistent methodology - - - #Back-end proficiency - key: options.backend_proficiency.0 - t: Not able to handle any back-end work - - - key: options.backend_proficiency.1 - t: Able to set up all-in-one CMSs (WordPress, etc.) or static site generators (Jekyll, etc.) - - - key: options.backend_proficiency.2 - t: Able to develop apps using pre-existing frameworks (Rails, Laravel, etc.) - - - key: options.backend_proficiency.3 - t: Setting up an entire back-end from scratch (Go, Node.js, etc.) - - - key: options.backend_proficiency.4 - t: Able to handle complex multi-server or microservices architectures - #Proficiency (generic versions) key: options.proficiency.0 @@ -1282,6 +1206,13 @@ translations: - key: user_info.higher_education_degree.description t: Do you have a higher education degree? + - + #completion + key: user_info.completion_stats + t: Survey Completion + - + key: user_info.completion_stats.description + t: Which proportion of the survey did respondents fill out? - #email_temporary (receive updates?) key: user_info.email_temporary From 27d89d064ffe829b0c84d6861343896282ee1e8e Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:15 +0900 Subject: [PATCH 1903/1932] New translations homepage.yml (Vietnamese) --- vi/homepage.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/vi/homepage.yml b/vi/homepage.yml index 34b73e3c64d..9ce73f294d6 100644 --- a/vi/homepage.yml +++ b/vi/homepage.yml @@ -60,16 +60,16 @@ translations: t: Preview Questions - #newsletter - key: homepage.newsletter.stay_tuned + key: newsletter.stay_tuned t: Don't Miss the Next Survey - - key: homepage.newsletter.leave_your_email + key: newsletter.leave_your_email t: Leave us your email and we’ll let you know when the next survey takes place. - - key: homepage.newsletter.email + key: newsletter.email t: Your Email - - key: homepage.newsletter.submit + key: newsletter.submit t: Notify Me - #languages From 11be8bf84006ac7e4eb882780f0a5f964f924a6f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:16 +0900 Subject: [PATCH 1904/1932] New translations state_of_js_2021_results.yml (Vietnamese) --- vi/state_of_js_2021_results.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/vi/state_of_js_2021_results.yml b/vi/state_of_js_2021_results.yml index 5bcff86c7d0..422a65eab95 100644 --- a/vi/state_of_js_2021_results.yml +++ b/vi/state_of_js_2021_results.yml @@ -19,12 +19,16 @@ translations: A lot happened in 2021. So much in fact that the survey was pushed back all the way to 2022! + Between a slew of faster build tools and a new crop of back-end frameworks, the JavaScript world kept evolving. And we did our best to keep up, giving this survey a couple new power-ups ([read more about what's new](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej)) such as new question types, the ability to cross-reference two datapoints (such as yearly salaries by experience level), and even a way to customize the charts to surface your own insights! Read more about [what's new this year](https://dev.to/sachagreif/whats-new-in-the-2021-state-of-javascript-survey-4eej) (English). + It wasn't all smooth sailing, though. We had to deal with a [data leak](https://dev.to/sachagreif/disclosing-a-state-of-javascriptstate-of-css-data-breach-2lg1) that thankfully didn't seem to have any bad consequences. And we're constantly making efforts to make the survey more inclusive, more accessible, and more fair. + Still, even though the survey can ever only represents a tiny, tiny part of the JavaScript ecosystem, we hope you'll find the resulting data interesting! + – Sacha Greif - ########################################################################### From e1f8112f15da95d95c17444ba08c02ccc4dc1b1b Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:17 +0900 Subject: [PATCH 1905/1932] New translations state_of_graphql.yml (Vietnamese) --- vi/state_of_graphql.yml | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/vi/state_of_graphql.yml b/vi/state_of_graphql.yml index fe66302b7f2..f909b809139 100644 --- a/vi/state_of_graphql.yml +++ b/vi/state_of_graphql.yml @@ -13,6 +13,14 @@ translations: But that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. Now, for the first time ever we're surveying the GraphQL community to figure out which of these many tools are the most popular, and which features are actually being used. With your help, let's see what GraphQL has been up to in 2022! + - + key: general.state_of_graphql.results_intro + t: > + When GraphQL was first introduced it offered a radically new way to build APIs, with more control, more granularity, and more flexibility. + + However, that flexibility came at a price in the form of extra complexity, and a crop of frameworks, libraries, and services quickly appeared to help define better patterns and workflows. + + Over 2000 developers took the first ever State of GraphQL survey to help us find out if they succeeded. And while this is only a tiny part of the overall GraphQL ecosystem, we - key: general.state_of_graphql.description t: The annual developer survey of the GraphQL ecosystem @@ -52,6 +60,9 @@ translations: - key: sections.security_performance.description t: Making your API more robust. + - + key: sections.other_features.title + t: Other Features - key: sections.graphql_servers.title t: GraphQL Servers @@ -94,6 +105,12 @@ translations: - key: sections.usage_graphql.description t: How you use GraphQL. + - + key: sections.tools_others.title + t: Other Tools + - + key: sections.tools_others.description + t: Other GraphQL tools. - ########################################################################### #Features @@ -341,6 +358,18 @@ translations: - key: usage.graphql_pain_points.others t: Other GraphQL Pain Points + - + key: happiness.graphql_servers + t: How happy are you with the overall state of GraphQL servers? + - + key: happiness.graphql_clients + t: How happy are you with the overall state of GraphQL clients? + - + key: happiness.graphql_api_generators + t: How happy are you with the overall state of API generators? + - + key: happiness.schema_builders + t: How happy are you with the overall state of schema builders? - key: happiness.state_of_graphql t: How happy are you with the overall state of the GraphQL ecosystem? From 9b142c93a5091c86b5676040abcd39242eabb5a8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:21 +0900 Subject: [PATCH 1906/1932] New translations state_of_graphql_2022.yml (Japanese) --- ja/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 ja/state_of_graphql_2022.yml diff --git a/ja/state_of_graphql_2022.yml b/ja/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/ja/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From f503187202a09b89fb8706d6ecb97a8f53fa8fad Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:22 +0900 Subject: [PATCH 1907/1932] New translations legacy.yml (Korean) --- ko/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 ko/legacy.yml diff --git a/ko/legacy.yml b/ko/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/ko/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From e00ca7e59c546d7c824a678ed93035618957a712 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:23 +0900 Subject: [PATCH 1908/1932] New translations legacy.yml (Turkish) --- tr/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 tr/legacy.yml diff --git a/tr/legacy.yml b/tr/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/tr/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 21816a783d8be5eda32222c8c1fde08c1884fe34 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:24 +0900 Subject: [PATCH 1909/1932] New translations legacy.yml (Portuguese, Brazilian) --- pt/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 pt/legacy.yml diff --git a/pt/legacy.yml b/pt/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/pt/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 35ba126022ce45f9ae113c2737764f76ea5884c9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:25 +0900 Subject: [PATCH 1910/1932] New translations state_of_graphql_2022.yml (Vietnamese) --- vi/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 vi/state_of_graphql_2022.yml diff --git a/vi/state_of_graphql_2022.yml b/vi/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/vi/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 0b089ef0a12f45be10e5f5dadb944dd0b753d8e8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:27 +0900 Subject: [PATCH 1911/1932] New translations legacy.yml (Vietnamese) --- vi/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 vi/legacy.yml diff --git a/vi/legacy.yml b/vi/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/vi/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From ecc2619dc1754014f27d90d67011bbc44e9b0dbe Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:28 +0900 Subject: [PATCH 1912/1932] New translations state_of_graphql_2022.yml (English) --- en/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 en/state_of_graphql_2022.yml diff --git a/en/state_of_graphql_2022.yml b/en/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/en/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 98221b7d2c9f515d168a999979e49730b77db58f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:29 +0900 Subject: [PATCH 1913/1932] New translations legacy.yml (English) --- en/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 en/legacy.yml diff --git a/en/legacy.yml b/en/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/en/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 55c8a3eafbd3df9bb051ebd534983a141bf98c3c Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:30 +0900 Subject: [PATCH 1914/1932] New translations state_of_graphql_2022.yml (Chinese Traditional) --- zh/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 zh/state_of_graphql_2022.yml diff --git a/zh/state_of_graphql_2022.yml b/zh/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/zh/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 2d9db01ff52de729e657dca3af162e4b5e88eac8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:31 +0900 Subject: [PATCH 1915/1932] New translations legacy.yml (Chinese Traditional) --- zh/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 zh/legacy.yml diff --git a/zh/legacy.yml b/zh/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/zh/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From aa457189a1873822c5945bd3d290a7a7ece5421a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:34 +0900 Subject: [PATCH 1916/1932] New translations state_of_graphql_2022.yml (Ukrainian) --- uk/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 uk/state_of_graphql_2022.yml diff --git a/uk/state_of_graphql_2022.yml b/uk/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/uk/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 9dbe56857a3e91e9e7b7fdcd0946ec583c6c7b57 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:35 +0900 Subject: [PATCH 1917/1932] New translations legacy.yml (Ukrainian) --- uk/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 uk/legacy.yml diff --git a/uk/legacy.yml b/uk/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/uk/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 53b9d9a08cc5c322c6ddc7c8aa4d97408ea06bcd Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:36 +0900 Subject: [PATCH 1918/1932] New translations state_of_graphql_2022.yml (Turkish) --- tr/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 tr/state_of_graphql_2022.yml diff --git a/tr/state_of_graphql_2022.yml b/tr/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/tr/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 4f7890b81866cd376ef4881cbd1fb16283156789 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:37 +0900 Subject: [PATCH 1919/1932] New translations state_of_graphql_2022.yml (Swedish) --- sv/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 sv/state_of_graphql_2022.yml diff --git a/sv/state_of_graphql_2022.yml b/sv/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/sv/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 4eecc5076cd9e35b3af7d43ac01aef1f0c3f3e01 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:38 +0900 Subject: [PATCH 1920/1932] New translations state_of_graphql_2022.yml (Korean) --- ko/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 ko/state_of_graphql_2022.yml diff --git a/ko/state_of_graphql_2022.yml b/ko/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/ko/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From fbe8186d3515167b2509d75698ca795508f05fb9 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:39 +0900 Subject: [PATCH 1921/1932] New translations legacy.yml (Swedish) --- sv/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 sv/legacy.yml diff --git a/sv/legacy.yml b/sv/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/sv/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From b48576b7ddc4ddc8e229dc722e4b6ea12d5b4166 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:40 +0900 Subject: [PATCH 1922/1932] New translations state_of_graphql_2022.yml (Serbian (Cyrillic)) --- sr/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 sr/state_of_graphql_2022.yml diff --git a/sr/state_of_graphql_2022.yml b/sr/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/sr/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 730a417946c00e1e695d3aa17b5fc08348d1d0f1 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:41 +0900 Subject: [PATCH 1923/1932] New translations legacy.yml (Serbian (Cyrillic)) --- sr/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 sr/legacy.yml diff --git a/sr/legacy.yml b/sr/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/sr/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 5e9e7bb7fc017cb1ba5519fa9ff1e1cd12915668 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:43 +0900 Subject: [PATCH 1924/1932] New translations state_of_graphql_2022.yml (Russian) --- ru/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 ru/state_of_graphql_2022.yml diff --git a/ru/state_of_graphql_2022.yml b/ru/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/ru/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 13769338eea2c60d2f863d08966fa361c65a0177 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:44 +0900 Subject: [PATCH 1925/1932] New translations legacy.yml (Russian) --- ru/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 ru/legacy.yml diff --git a/ru/legacy.yml b/ru/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/ru/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From a1450ed0f828b370349c8292bd2b49a0b57a76e5 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:45 +0900 Subject: [PATCH 1926/1932] New translations state_of_graphql_2022.yml (Portuguese) --- pt/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 pt/state_of_graphql_2022.yml diff --git a/pt/state_of_graphql_2022.yml b/pt/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/pt/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 3602f4491308fbfd26337cd6ac3f2be23101fb5f Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:48 +0900 Subject: [PATCH 1927/1932] New translations state_of_graphql_2022.yml (Polish) --- pl/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 pl/state_of_graphql_2022.yml diff --git a/pl/state_of_graphql_2022.yml b/pl/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/pl/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 50600f4eea8e7501ccc5dbc532400adf4461973a Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:49 +0900 Subject: [PATCH 1928/1932] New translations legacy.yml (Polish) --- pl/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 pl/legacy.yml diff --git a/pl/legacy.yml b/pl/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/pl/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 2848e23846db0f3b7ebe54ae7355f322128400a0 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:50 +0900 Subject: [PATCH 1929/1932] New translations state_of_graphql_2022.yml (Norwegian) --- no/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 no/state_of_graphql_2022.yml diff --git a/no/state_of_graphql_2022.yml b/no/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/no/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 1814ff769e350d725f5377360924be720c5d5dde Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:51 +0900 Subject: [PATCH 1930/1932] New translations legacy.yml (Norwegian) --- no/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 no/legacy.yml diff --git a/no/legacy.yml b/no/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/no/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above From 8a58d37eb526b4734e5e53239a04f0b5c05b32c8 Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:53 +0900 Subject: [PATCH 1931/1932] New translations state_of_graphql_2022.yml (Dutch) --- nl/state_of_graphql_2022.yml | 427 +++++++++++++++++++++++++++++++++++ 1 file changed, 427 insertions(+) create mode 100644 nl/state_of_graphql_2022.yml diff --git a/nl/state_of_graphql_2022.yml b/nl/state_of_graphql_2022.yml new file mode 100644 index 00000000000..59cdf23826f --- /dev/null +++ b/nl/state_of_graphql_2022.yml @@ -0,0 +1,427 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + key: general.results.description + t: The 2022 edition of the annual survey about the latest trends in the GraphQL ecosystem. + - + key: general.livestream_announcement + t: Make sure to tune in for our [special survey results livestream](https://dev.to/sachagreif/state-of-javascript-2021-livestream-24a5) on February 22! (English) + - + ########################################################################### + #Introduction + ########################################################################### + key: sections.introduction.description + t: > + + Since being originally created at Facebook in September 2015, many developers have embraced GraphQL as a new and promising way to build APIs. + + Yet 7 years later, a lot of questions still remain: when do you need GraphQL exactly? Should you hand-code your GraphQL API or generate it from your database? And will it ever replace REST? + + To answer these questions and many more, we've created the first ever **State of GraphQL** community survey. Over 3,000 developers took part this year, and this is just the beginning. + + We hope you enjoy browsing the data, and make sure to check out our [GraphQL API](https://graphiql.devographics.com/) as well! + + – Sacha Greif + - + ########################################################################### + #Tshirt + ########################################################################### + key: sections.tshirt.title + t: T-shirt + - + key: sections.tshirt.description + t: | + ## Support the Survey With the State of JavaScript T-Shirt + + Between the bad video quality, the bulky cassettes, and having to rewind, there's not much to miss about the VHS era. But one thing we *do* miss are the amazing 90s visuals that used to adorn blank VHS tapes. + + But now, thanks to the talented Christopher Kirk-Nielsen you can enjoy all this retro radness while also celebrating your love for JavaScript at the same time! + - + key: tshirt.about + t: About the T-shirt + - + key: tshirt.description + t: | + We use a high-quality, super-soft tri-blend shirt with a slim fit printed by our partners at Cotton Bureau. + - + key: tshirt.getit + t: Get It + - + key: tshirt.price + t: USD $29 + shipping + - + key: tshirt.designer.heading + t: About the Designer + - + key: tshirt.designer.name + t: Christopher Kirk-Nielsen + - + key: tshirt.designer.bio + t: | + Originally from France but now based in the United States, Chris is not just an amazing front-end developer, but also a talented illustrator who specializes in retro visuals. In fact, we encourage you to also check out his [other t-shirt designs](https://chriskirknielsen.com/designs)! + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.description + t: | + **3,094** respondents took part in this year's survey. + - + key: sections.features.description + t: | + GraphQL may be a simple concept at its core, but there are many features and patterns to consider when you dig below the surface. + - + key: sections.libraries.description + t: | + The GraphQL ecosystem is surprisingly deep, with many competing libraries helping you set up your API. + - + key: sections.tools_others.description + t: | + Picking the right tools to use in combination with GraphQL can make all the difference. + - + key: sections.usage.description + t: | + We wanted to know not only how people use GraphQL, but also *why* they use it – as well as where GraphQL is still lacking… + - + key: sections.resources.description + t: | + We're sure you'll discover at least one or two new people, podcasts, or blogs to follow! + - + key: sections.opinions.description + t: | + Whether it's pain points that hold you back today, or missing features that you hope to use + tomorrow, this was your chance to vent and share your gripes with JavaScript! + - + ########################################################################### + #Charts + ########################################################################### + key: options.features_categories.graphql_language + aliasFor: sections.graphql_language.title + - + key: options.features_categories.directives + aliasFor: sections.directives.title + - + key: options.features_categories.security_performance + aliasFor: sections.security_performance.title + - + key: options.features_categories.other_features + aliasFor: sections.other_features.title + - + key: blocks.tools_quadrant.description + t: | + This chart shows each technology's **satisfaction ratio** (or **interest ratio**) over its total **user count**. + It can be divided into four quadrants: + + - **1**: Low usage, high satisfaction. Technologies worth keeping an eye on. + + - **2**: High usage, high satisfaction. Safe technologies to adopt. + + - **3**: Low usage, low satisfaction. Technologies that are harder to recommend currently. + + - **4**: High usage, low satisfaction. Reassess these technologies if you're currently using them. + - + ########################################################################### + #Notes + ########################################################################### + key: blocks.gender.note + t: | + If you're interested in learning more, we [wrote a blog post](https://dev.to/sachagreif/is-our-survey-biased-against-women-49oj) that addresses the survey's gender dynamics. + - + key: blocks.currently_missing_from_css.note + t: | + You can explore the full dataset of answers to this question in [this side project](https://whatsmissingfromcss.com/). + - + key: blocks.source.note + t: > + + This chart aggregates a mix of referrers, URL parameters, and freeform answers. + - State of JS: the [State of JS](https://stateofjs.com) mailing list. + - State of CSS: the State of CSS mailing list; also matches `email`, `by email`, etc. + - Work: matches `work`, `colleagues`, `coworkers`, etc. + - + ########################################################################### + #Awards + ########################################################################### + key: award.feature_adoption_delta_award.comment + t: With a **{value}** progression in 2021, the nullish coalescing operator (??) has quickly become an integral part of JavaScript. + - + key: award.tool_usage_delta_award.comment + t: esbuild is barely two years old, but with a **{value}** progression over the last year it's already gaining ground. + - + key: award.tool_satisfaction_award.comment + t: Vite takes the top spot with a sky-high **{value}** satisfaction ratio! + - + key: award.tool_interest_award.comment + t: With a **{value}** interest ratio, Vite once again wins the gold! + - + key: award.most_write_ins_award.comment + t: Many questions also accepted write-in answers, and with **{value}** mentions Elm was the most popular item overall. + - + ########################################################################### + #Conclusion + ########################################################################### + key: sections.conclusion.description + t: | + + JavaScript is in a tremendously better state today compared to 2016. + + Back when the first State of JS survey took place, only 21% of you used TypeScript compared to 69% today. Whereas we used to joke about a new front end framework releasing every day, **React** and **Vue** have now been dominant for 6 years running. And the percentage of people reporting that "JS is moving too fast" is down from 59% to 38%. + + This is not to say that the language has stood still. The **Optional Chaining** and **Nullish Coalescing** APIs have rocketed up to be the most used new APIs in our survey, despite only being 2 years old. And more good things are on the way from TC39: you reported that date management is a top missing feature, and the Temporal API recently reached [Stage 3](https://github.com/tc39/proposal-temporal). + + The tooling ecosystem is also seeing its own rapid evolution, and it's fair to say that 2021 has been the year of **Vite**. Vite not only debuted at 98% satisfaction, but usage is already at 30% in its first year on our survey, even eclipsing esbuild. Vite isn't alone in trying to improve the state of JavaScript build tools - 8 of the 12 tools we track today are less than two years old! And while **pnpm**, **Turborepo**, and **Nx** took the top spots in our first year tracking monorepo tooling, only 25% report being happy with the state of that category, showing that a lot of work remains to be done. + + Also notable: many new entrants like **Deno**, **Rome**, **Astro**, **Remix**, and more are now supported by venture-backed companies, perhaps charting a viable alternative to the fragile open-source funding environment. + + As the [Third Age of JavaScript](https://www.swyx.io/js-third-age/) enters its third year, the opportunities for aspiring open sourcerors and entrepreneurs continue to unfold, and I'm excited to see what the next couple years bring! + - + key: conclusion.bio + t: Head of DX at Temporal + - + ########################################################################### + #Picks + ########################################################################### + key: picks.my_pick + t: 'My 2022 Pick: ' + - + key: picks.intro + t: We asked members of the GraphQL community to share their “pick of the year” + - + key: picks.jamie_barton.name + t: GraphQL Mesh + - + key: picks.jamie_barton.bio + t: Full Stack Developer & Educator + - + key: picks.jamie_barton.description + t: | + More and more people are looking for solutions to bridge the + gap between all of their services. Mesh lets you do that with GraphQL, + and non-GraphQL services. + - + key: picks.tanmai_gopal.name + t: Streaming over GraphQL Subscriptions + - + key: picks.tanmai_gopal.bio + t: CEO & co-founder at Hasura + - + key: picks.tanmai_gopal.description + t: | + Modern APIs need to handle an increasing volume of data, + or fast-moving data that is a stream. + Could we use GraphQL subscriptions as a streaming API? + - + key: picks.tim_suchanek.name + t: Benjie Gillam + - + key: picks.tim_suchanek.bio + t: Software Engineer and Entrepreneur + - + key: picks.tim_suchanek.description + t: | + Benjie is one of the main people pushing GraphQL forward. + His engagement in the WG, TSC, and various foundation initiatives is second to none. + - + key: picks.shawn_wang.name + t: Supabase + - + key: picks.shawn_wang.bio + t: Head of DX at Temporal + - + key: picks.shawn_wang.description + t: | + Supabase is making Postgres accessible to more developers and showing + everyone how a small focused team can out-ship peers 10x their size. + - + key: picks.sarah_drasner.name + t: Pawel Kozlowski + - + key: picks.sarah_drasner.bio + t: Director of Engineering, Core Developer Web at Google + - + key: picks.sarah_drasner.description + t: | + Pawel Kozlowski is the kind of developer who can be open-minded to different + approaches with humility and curiosity with the interest of improving things. + - + key: picks.sara_vieira.name + t: Paul Henschel + - + key: picks.sara_vieira.bio + t: International Agent of JS Bullshit + - + key: picks.sara_vieira.description + t: | + Paul's work on animations and ReactThreeFiber + have made doing any kind of 3D work on the web way easier. + - + key: picks.mark_erikson.name + t: Ryan Carniato + - + key: picks.mark_erikson.bio + t: Redux Maintainer + - + key: picks.mark_erikson.description + t: | + Ryan's reactive JS framework SolidJS hit 1.0, + and he wrote numerous articles analyzing advanced + JS framework implementation concepts. + - + key: picks.miguel_angel_duran.name + t: Vite + - + key: picks.miguel_angel_duran.bio + t: Front End Dev & Twitch Coding Streamer + - + key: picks.miguel_angel_duran.description + t: | + In addition to esbuild and swc, fantastic tools pushing forward the ecosystem, + I'm enjoying Vite. It has a delightful DX, and it's rich in features. + - + key: picks.alyssa_nicoll.name + t: BroccoDev's Twitch Stream + - + key: picks.alyssa_nicoll.bio + t: Sr. Developer Advocate at Progress + - + key: picks.alyssa_nicoll.description + t: | + Mike Brocchi recently started streaming to Twitch. He is a brilliant programmer, + developer, and most importantly teacher. + I always have a blast watching his streams and learning from him. + - + key: picks.michael_jackson.name + t: esbuild + - + key: picks.michael_jackson.bio + t: Co-founder of Remix + - + key: picks.michael_jackson.description + t: | + We have been building the Remix compiler on top of esbuild and it + has definitely raised the bar as far as JS bundlers are concerned. + It's incredibly fast and the plugin API allows us to do pretty much anything we want. + - + key: picks.david_khourshid.name + t: Remix + - + key: picks.david_khourshid.bio + t: Pianist and founder of Stately + - + key: picks.david_khourshid.description + t: | + Remix is a full-stack web framework that feels old-school, but in a good way, + by putting you on the path to create fast, complex, and accessible modern web apps. + - + key: picks.kent_c_dodds.name + t: Fly.io + - + key: picks.kent_c_dodds.bio + t: Director of Developer Experience, Remix + - + key: picks.kent_c_dodds.description + t: | + Fly enabled me (a frontend engineer with a distain for DevOps) + to confidently deploy a real-world, globally-distributed, production-grade + app. + - + key: picks.tejas_kumar.name + t: Joe Haddad + - + key: picks.tejas_kumar.bio + t: Web Developer, Conference Speaker, and Director of DevRel at Xata + - + key: picks.tejas_kumar.description + t: | + Joe works on Next.js at Vercel and is constantly looking to proudly + demonstrate its power while actively listening + to feedback from the community to support them better. + - + key: picks.wes_bos.name + t: TC39 Proposals + - + key: picks.wes_bos.bio + t: JavaScript Teacher & Podcast Host + - + key: picks.wes_bos.description + t: | + A Git repo full of all the things that have been proposed to be added to JavaScript. It's really fun to read through all the ideas people have for the language and see them go through the stages. + - + key: picks.scott_tolinkski.name + t: SvelteKit + - + key: picks.scott_tolinkski.bio + t: Creator of Level-Up Tuts, co-host of Syntax + - + key: picks.scott_tolinkski.description + t: | + Svelte Kit provides the amazing developer experience of Svelte with all + of the modern features of expected from a web platform. + - + key: picks.xxxx.name + t: + - + key: picks.xxxx.bio + t: + - + key: picks.xxxx.description + t: | + + - + ########################################################################### + #Sponsors + ########################################################################### + key: partners.frontendmasters.description + t: Advance your skills with in-depth, modern front-end engineering courses. + - + key: partners.polypane.description + t: The browser for ambitious devs. Build responsive, accessible and fast websites with ease. + - + key: partners.google_chrome.description + t: Thanks to the Google Chrome team for supporting our work. + - + ########################################################################### + #FAQ/About + ########################################################################### + key: about.content + t: > + The 2021 State of JS survey ran from January 13 to February 2 **2022**, and collected 16,085 responses. The survey is run by me, [Sacha Greif](https://sachagreif.com/), with help from a team of open-source contributors and consultants. + This year's logo and t-shirt were designed by [Christopher Kirk-Nielsen](http://chriskirknielsen.com/). + ### Survey Goals + This survey, along with the [State of CSS](https://stateofcss.com/) survey, was created to identify upcoming trends in the web development ecosystem in order to help developers make technological choices. + As such, these surveys are focused on anticipating what's coming over the next few years rather than analyzing what's popular now, which is why the features or technologies that are currently most widespread are not always included. + They should also be taken as a **snapshot of a specific subset of developers**, and are not meant to speak for the entire ecosystem. + ### Survey Design + The survey was designed in part based on last year's survey, with an open feedback period where the survey outline was discussed [on GitHub](https://github.com/StateOfJS/Monorepo/issues/56). + All survey questions were optional. + ### Survey Audience + The survey was openly accessible online and respondents were not filtered or selected in any way. Respondents were primarily a mix of respondents from past surveys (alerted through a dedicated mailing list) and social media traffic. + Note that frameworks, libraries, etc. were free to encourage their audience to participate in the survey and some of them did take advantage of this via banners, tweets, etc. A detailed breakdown of traffic sources is included in the "Sources" chart. + ### Representativeness & Inclusivity + While we believe it's important to give a voice to every community, the reality is that an open survey like this one will always struggle to properly represent everybody, especially when operating through systems that already carry their own inherent biases. + + In order to counter-balance this, we are implementing three distinct strategies: + + - **Outreach**: we always try to reach out to different organizations (such as BIPOC- or LGBTQ-focused organizations, or online teaching platforms) to try and diversify our own audience. + - **Data Analysis**: through features like facets and variants, we're always trying to make it easier to surface the voices of any demographic segment, no matter how minoritized it might be in our data. + - **Barrier Lowering**: making the survey too long, inaccessible, slow to load, English-only, etc. can all contribute to imposing an "effort tax" that cuts off the parts of the community that can't afford to pay it. Fixing these issues can lower the barrier to entry and in the process make our audience more diverse. + ### Project Funding + Funding from this project comes from a variety of sources: + + - **T-shirt sales**. + - **Chart Sponsorships**: members of the community can donate to the survey in exchange for having their name featured in the report. + - **Sponsored links**: the links to recommended resources at the bottom of each page are provided by our partner [Frontend Masters](https://frontendmasters.com/). + - **Other Funding**: this year, the [Google Chrome](https://www.google.com/chrome/) team set aside a small budget to help hire an [accessibility consultant](https://fossheim.io/) to work on the CSS and JS surveys. + + Despite these funding sources, the surveys remains mostly a self-funded project overall and any contribution or sponsorship would be greatly appreciated. I would especially like to work closely with more browser vendors, since they play such a central role in the web ecosystem. + ### Technical Overview + You can find a more in-depth technical overview of how the surveys are run [here](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb). + - **Data collection**: custom [Vulcan.js](http://vulcanjs.org/) app. + - **Data storage/processing**: MongoDB & MongoDB Aggregations. + - **Data API**: Node.js GraphQL API. + - **Results Site**: [Gatsby](https://www.gatsbyjs.com/) React app. + - **Data Visualizations**: [Nivo](https://nivo.rocks/) React dataviz library. + - **Type**: [IBM Plex Mono](https://fonts.google.com/specimen/IBM+Plex+Mono) and [Bebas Neue](https://fonts.google.com/specimen/Bebas+Neue). From 8c46e1c926567cc18e9bb39ce381186fdab06cdb Mon Sep 17 00:00:00 2001 From: Sacha Greif Date: Tue, 6 Sep 2022 20:29:54 +0900 Subject: [PATCH 1932/1932] New translations legacy.yml (Dutch) --- nl/legacy.yml | 1389 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1389 insertions(+) create mode 100644 nl/legacy.yml diff --git a/nl/legacy.yml b/nl/legacy.yml new file mode 100644 index 00000000000..93783f54c4f --- /dev/null +++ b/nl/legacy.yml @@ -0,0 +1,1389 @@ +locale: en-US +translations: + - + ########################################################################### + #General + ########################################################################### + #homepage + key: general.why_create_account + t: Why do I need to create an account? + - + key: general.create_account_reasons + t: > + We ask you to create an account in order to: + - Avoid duplicate responses + - Give you access to your data + - Save your session as you go + - Notify you when results are live + - + key: general.survey_closed + t: > + Sorry, the survey is now closed! You can still review your data but you won't be able to modify it. + - + key: general.survey_read_only + t: > + You are currently viewing this survey in read-only mode. + - + key: general.survey_preview + t: > + This survey is in preview mode. Its questions are subject to change, and all inputted data will be deleted when the actual survey starts. + - + key: general.survey_read_only_back + t: > + Go back to the main survey page to start or resume a session. + - + key: general.take_survey + t: Take the {name} survey + - + #surveys + key: general.open_surveys + t: Open Surveys + - + key: general.no_open_surveys + t: No surveys are currently open. + - + key: general.closed_surveys + t: Closed Surveys + - + key: general.no_closed_surveys + t: No surveys are currently closed. + - + key: general.preview_surveys + t: Preview Surveys + - + key: general.no_preview_surveys + t: No surveys available to preview. + - + key: general.start_survey + t: Start Survey » + - + key: general.continue_survey + t: Continue Survey » + - + key: general.review_survey + t: Review Survey » + - + key: general.preview_survey + t: Preview Survey » + - + key: general.finish_survey + t: Finish Survey » + - + key: general.next_section + t: Next section + - + key: general.prev_section + t: Previous section + - + key: general.survey_closed + t: This survey is now closed. + - + key: general.survey_results + t: View Survey Results » + - + key: general.surveys_available_languages + t: 'Surveys available in:' + - + key: general.help_us_translate + t: Help us translate the surveys » + - + key: general.translators + t: Translators + - + key: general.translation_help + t: Translation Help + - + key: general.newly_added + t: Newly added this year + - + key: general.new + t: New + - + key: general.devographics_banner + t: Devographics is the new name of the collective running the State of JavaScript, CSS, and GraphQL surveys. + - + #credits + key: credits.thanks + t: Special Thanks + - + key: credits.contributors + t: Contributors + - + key: credits.contributors.description + t: Special thanks to the following people for helping us design the survey. + - + key: credits.accessibility + t: Accessibility Consulting + - + key: credits.survey_design + t: Survey Design + - + key: credits.logo_design + t: Logo Design + - + key: credits.mobile_testing + t: Mobile Testing + - + key: credits.data_visualizations + t: Data Visualizations + - + key: credits.repo_architecture + t: Repo Architecture + - + key: credits.code_refactoring + t: Code Refactoring + - + key: credits.data_processing + t: Data Processing + - + #support + key: general.support_from + t: With Support From + - + #footer + key: general.privacy_policy + t: Privacy Policy + - + key: general.leave_issue + t: Questions? Found a bug? Leave an issue. + - + key: general.emoji_icons + t: Emoji icons by Icons8 + - + #navigation + key: general.table_of_contents + t: Table of Contents + - + key: general.all_questions_optional + t: > + Note: all questions are optional, reaching 100% completion is not required. + - + key: general.data_is_saved + t: Your data is saved whenever you navigate to the previous or next section. + - + key: general.close_nav + t: Close menu + - + key: general.open_nav + t: Open menu + - + key: general.more_actions + t: More actions + - + key: general.skip_to_content + t: Skip to content + - + #thanks + key: general.back + t: Back + - + key: general.thanks + t: > + Thanks for filling out the survey! Your data is saved. + + Also, you can help us get the word out by sharing this survey. Every bit counts, and it'll help make our data even more representative: + - + key: thanks.learn_more_about + t: 'Some of the features you might want to learn more about:' + - + key: thanks.knowledge_score + t: Knowledge Score + - + key: thanks.score_explanation + t: > + You’ve heard or used {known} out of {total} features mentioned in the survey, which puts you in the top {knowledgeRankingFromTop}% of all respondents. + - + key: thanks.share_on_twitter + t: Share on Twitter + - + key: thanks.share_score_message + t: > + I got a {score}% knowledge score on this year's #{hashtag} survey! Take the survey here: {shareUrl} #{hashtag} survey! Take the survey here: {shareUrl} + - + #share + key: general.share_subject + t: > + {surveyName} survey + - + key: general.share_text + t: > + This year's {surveyName} survey is now open! {link} + - + #forms + key: forms.select_option + t: Select option + - + key: forms.clear_field + t: Clear question + - + #partners + key: partners.our_partners + t: Our Partners + - + key: partners.become_partner + t: Become a partner + - + #404 + key: notfound.title + t: 404 Not Found + - + key: notfound.description + t: Sorry, we couldn't find what you were looking for. + - + #other + key: general.join_discord + t: Join us on Discord. + - + key: general.translator_mode + t: Press option/alt to enable translator mode. + - + key: general.charts_nivo + t: Charts built with Nivo. + - + key: general.made_by_devographics + t: Made by Devographics + - + ########################################################################### + #Nav + ########################################################################### + key: nav.surveys + t: Surveys + - + key: nav.account + t: Account + - + ########################################################################### + #Sections + ########################################################################### + key: sections.user_info.title + t: About You + - + key: sections.user_info.description + t: Let's get to know the real you. + - + key: sections.features.title + t: Features + - + key: sections.features.description + t: Syntax, keywords, and other language features. + - + key: sections.resources.title + t: Resources + - + key: sections.resources.description + t: What {topic} resources do you consult? + - + key: sections.opinions.title + t: Opinions + - + key: sections.opinions.description + t: How do you feel about the state of {topic}? + - + key: sections.other_tools.title + t: Other Tools + - + key: sections.other_tools.description + t: For these tools & technologies, just check the ones that you use regularly. + - + key: sections.report.title + t: Trend Report + - + ########################################################################### + #Options + ########################################################################### + #features + key: options.features.never_heard + t: Never heard of it/Not sure what it is + - + key: options.features.heard + t: Know what it is, but haven't used it + - + key: options.features.used + t: I've used it + - + #features (no emoji) + key: options.features.never_heard.label + t: Never heard of it/Not sure what it is + - + key: options.features.heard.label + t: Know what it is, but haven't used it + - + key: options.features.used.label + t: I've used it + - + #features (short versions) + key: options.features.never_heard.short + t: Never heard of it + - + key: options.features.heard.short + t: Know about it + - + key: options.features.used.short + t: Have used it + - + #patterns + key: options.patterns.use_never + t: Almost always avoid + - + key: options.patterns.use_sparingly + t: Use sparingly + - + key: options.patterns.use_neutral + t: Neutral + - + key: options.patterns.use_frequently + t: Use frequently + - + key: options.patterns.use_always + t: Use as much as I can + - + #tools experience + key: options.tools.never_heard + t: Never heard of it/Not sure what it is + - + key: options.tools.interested + t: Heard of it > Would like to learn + - + key: options.tools.not_interested + t: Heard of it > Not interested + - + key: options.tools.would_use + t: Used it > Would use again + - + key: options.tools.would_not_use + t: Used it > Would not use again + - + #tools experience (no emoji) + key: options.tools.never_heard.legend + t: Never heard of it/Not sure what it is + - + key: options.tools.interested.legend + t: Heard of it > Would like to learn + - + key: options.tools.not_interested.legend + t: Heard of it > Not interested + - + key: options.tools.would_use.legend + t: Used it > Would use again + - + key: options.tools.would_not_use.legend + t: Used it > Would not use again + - + #tools experience (short versions) + key: options.tools.never_heard.short + t: Never heard + - + key: options.tools.interested.short + t: Interested + - + key: options.tools.not_interested.short + t: Not interested + - + key: options.tools.would_use.short + t: Would use again + - + key: options.tools.would_not_use.short + t: Would not use + - + #happiness + key: options.happiness.0 + t: Very Unhappy + - + key: options.happiness.1 + t: Unhappy + - + key: options.happiness.2 + t: Neutral + - + key: options.happiness.3 + t: Happy + - + key: options.happiness.4 + t: Very Happy + - + #happiness (short version) + key: options.happiness.0.short + t: Very Unhappy + - + key: options.happiness.1.short + t: Unhappy + - + key: options.happiness.2.short + t: Neutral + - + key: options.happiness.3.short + t: Happy + - + key: options.happiness.4.short + t: Very Happy + - + #opinions + key: options.opinions.0 + t: Disagree Strongly + - + key: options.opinions.1 + t: Disagree + - + key: options.opinions.2 + t: Neutral + - + key: options.opinions.3 + t: Agree + - + key: options.opinions.4 + t: Agree Strongly + - + #age + key: options.age.range_less_than_10 + t: 10 years old or under + - + key: options.age.range_10_18 + t: 11-18 years old + - + key: options.age.range_18_24 + t: 19-24 years old + - + key: options.age.range_25_34 + t: 25-34 years old + - + key: options.age.range_35_44 + t: 35-44 years old + - + key: options.age.range_45_54 + t: 45-54 years old + - + key: options.age.range_55_64 + t: 55-64 years old + - + key: options.age.range_more_than_65 + t: 65 years or older + - + #age (short versions) + key: options.age.range_less_than_10.short + t: '<=10' + - + key: options.age.range_10_18.short + t: 11-18 + - + key: options.age.range_18_24.short + t: 19-24 + - + key: options.age.range_25_34.short + t: 25-34 + - + key: options.age.range_35_44.short + t: 35-44 + - + key: options.age.range_45_54.short + t: 45-54 + - + key: options.age.range_55_64.short + t: 55-64 + - + key: options.age.range_more_than_65.short + t: '>65' + - + #years of experience + key: options.years_of_experience.range_less_than_1 + t: Less than one year + - + key: options.years_of_experience.range_1_2 + t: 1 to 2 years + - + key: options.years_of_experience.range_2_5 + t: 3 to 5 years + - + key: options.years_of_experience.range_5_10 + t: 6 to 10 years + - + key: options.years_of_experience.range_10_20 + t: 11 to 20 years + - + key: options.years_of_experience.range_more_than_20 + t: More than 20 years + - + #years of experience (short versions) + key: options.years_of_experience.range_less_than_1.short + t: '<1 years' + - + key: options.years_of_experience.range_1_2.short + t: 1-2 years + - + key: options.years_of_experience.range_2_5.short + t: 3-5 years + - + key: options.years_of_experience.range_5_10.short + t: 6-10 years + - + key: options.years_of_experience.range_10_20.short + t: 11-20 years + - + key: options.years_of_experience.range_more_than_20.short + t: '>20 years' + - + #company size + key: options.company_size.range_1 + t: One employee + - + key: options.company_size.range_1_5 + t: 2 to 5 employees + - + key: options.company_size.range_5_10 + t: 6 to 10 employees + - + key: options.company_size.range_10_20 + t: 11 to 20 employees + - + key: options.company_size.range_20_50 + t: 21 to 50 employees + - + key: options.company_size.range_50_100 + t: 51 to 100 employees + - + key: options.company_size.range_100_1000 + t: 101 to 1000 employees + - + key: options.company_size.range_more_than_1000 + t: More than 1000 employees + - + #company size (short versions) + key: options.company_size.range_1.short + t: 1 + - + key: options.company_size.range_1_5.short + t: 1-5 + - + key: options.company_size.range_5_10.short + t: 6-10 + - + key: options.company_size.range_10_20.short + t: 11-20 + - + key: options.company_size.range_20_50.short + t: 21-50 + - + key: options.company_size.range_50_100.short + t: 51-100 + - + key: options.company_size.range_100_1000.short + t: 101-1000 + - + key: options.company_size.range_more_than_1000.short + t: '>1000' + - + #salary + key: options.yearly_salary.range_work_for_free + t: I work for free + - + key: options.yearly_salary.range_0_10 + t: '$0k-$10k' + - + key: options.yearly_salary.range_10_30 + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50 + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100 + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200 + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200 + t: More than $200k + - + #salary (short versions) + key: options.yearly_salary.range_work_for_free.short + t: '$0' + - + key: options.yearly_salary.range_0_10.short + t: '$0-$10k' + - + key: options.yearly_salary.range_10_30.short + t: '$10k-$30k' + - + key: options.yearly_salary.range_30_50.short + t: '$30k-$50k' + - + key: options.yearly_salary.range_50_100.short + t: '$50k-$100k' + - + key: options.yearly_salary.range_100_200.short + t: '$100k-$200k' + - + key: options.yearly_salary.range_more_than_200.short + t: '>$200k' + - + #Proficiency (generic versions) + key: options.proficiency.0 + t: None + - + key: options.proficiency.1 + t: Beginner + - + key: options.proficiency.2 + t: Intermediate + - + key: options.proficiency.3 + t: Advanced + - + key: options.proficiency.4 + t: Expert + - + #Gender + key: options.gender.female + t: Woman + - + key: options.gender.male + t: Man + - + key: options.gender.non_binary + t: Non-Binary or Gender Non-Conforming + - + key: options.gender.questioning + t: Questioning + - + key: options.gender.prefer_not_to_say + t: Prefer Not to Say + - + key: options.gender.not_listed + t: Not Listed + - + #Gender (short) + key: options.gender.female.short + t: Woman + - + key: options.gender.male.short + t: Man + - + key: options.gender.non_binary.short + t: Non-Binary or GNC + - + key: options.gender.questioning.short + t: Questioning + - + key: options.gender.prefer_not_to_say.short + t: Prefer Not to Say + - + key: options.gender.not_listed.short + t: Not Listed + - + #Race & Ethnicity + key: options.race_ethnicity.white_european + t: White + - + key: options.race_ethnicity.south_asian + t: South Asian + - + key: options.race_ethnicity.south_east_asian + t: South East Asian + - + key: options.race_ethnicity.hispanic_latin + t: Hispanic or Latino/Latina/Latinx + - + key: options.race_ethnicity.east_asian + t: East Asian + - + key: options.race_ethnicity.middle_eastern + t: Middle Eastern + - + key: options.race_ethnicity.black_african + t: Black or of African descent + - + key: options.race_ethnicity.multiracial + t: Multiracial + - + key: options.race_ethnicity.biracial + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian + t: Native American, Pacific Islander, or Indigenous Australian + - + key: options.race_ethnicity.not_listed + t: Not listed + - + #Race & Ethnicity (short) + key: options.race_ethnicity.white_european.short + t: White + - + key: options.race_ethnicity.south_asian.short + t: South Asian + - + key: options.race_ethnicity.south_east_asian.short + t: SE Asian + - + key: options.race_ethnicity.hispanic_latin.short + t: Hispanic/Latin + - + key: options.race_ethnicity.east_asian.short + t: East Asian + - + key: options.race_ethnicity.middle_eastern.short + t: Middle Eastern + - + key: options.race_ethnicity.black_african.short + t: Black/African Descent + - + key: options.race_ethnicity.multiracial.short + t: Multiracial + - + key: options.race_ethnicity.biracial.short + t: Biracial + - + key: options.race_ethnicity.native_american_islander_australian.short + t: Native American/Pacific Islander/Indigenous Australian + - + key: options.race_ethnicity.not_listed.short + t: Not listed + - + #Disability Status + key: options.disability_status.visual_impairments + t: > + Visual impairments (such as: blindness, color blindness, etc.) + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments (such as: deafness, tinnitus, etc.) + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments (such as: arthritis, carpal tunnel, etc.) + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments (such as: anxiety, dyslexia, etc.) + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Disability Status (short) + key: options.disability_status.visual_impairments + t: > + Visual impairments + - + key: options.disability_status.hearing_impairments + t: > + Hearing impairments + - + key: options.disability_status.mobility_impairments + t: > + Mobility impairments + - + key: options.disability_status.cognitive_impairments + t: > + Cognitive impairments + - + key: options.disability_status.not_listed + t: > + Not Listed + - + #Form Factors + key: options.form_factors.desktop + t: Desktop + - + key: options.form_factors.keyboard_only + t: Desktop with keyboard only + - + key: options.form_factors.smartphone + t: Smartphone + - + key: options.form_factors.feature_phone + t: Feature phone + - + key: options.form_factors.tablet + t: Tablet + - + key: options.form_factors.smart_watch + t: Smartwatch + - + key: options.form_factors.tv + t: TV + - + key: options.form_factors.gaming_console + t: Gaming console + - + key: options.form_factors.screen_reader + t: Screen reader + - + key: options.form_factors.print + t: Print + - + key: options.form_factors.testing_tools + t: Testing Tools (Axe, Lighthouse, etc.) + - + key: options.form_factors.vision_simulator + t: Altered Vision Simulator (color blindness, etc.) + - + #Industry Sector + key: options.industry_sector.ecommerce + t: Ecommerce & Retail + - + key: options.industry_sector.news_media + t: News, Media, & Blogging + - + key: options.industry_sector.healthcare + t: Healthcare + - + key: options.industry_sector.finance + t: Finance + - + key: options.industry_sector.programming_tools + t: Programming & Technical Tools + - + key: options.industry_sector.socialmedia + t: Social Media + - + key: options.industry_sector.marketing_tools + t: Marketing/Sales/Analytics Tools + - + key: options.industry_sector.education + t: Education + - + key: options.industry_sector.real_estate + t: Real Estate + - + key: options.industry_sector.government + t: Government + - + key: options.industry_sector.entertainment + t: Entertainment + - + key: options.industry_sector.consulting + t: Consulting & Services + - + key: options.industry_sector.travel + t: Travel + - + key: options.industry_sector.insurance + t: Insurance + - + key: options.industry_sector.logistics + t: Logistics + - + key: options.industry_sector.energy + t: Energy + - + key: options.industry_sector.telecommunications + t: Telecommunications + - + key: options.industry_sector.student + t: Student + - + key: options.industry_sector.hospitality + t: Hospitality + - + key: options.industry_sector.cyber_security + t: Cyber Security + - + key: options.industry_sector.construction + t: Construction + - + key: options.industry_sector.automotive + t: Automotive + - + key: options.industry_sector.agriculture + t: Agriculture + - + key: options.industry_sector.transport + t: Transport + - + key: options.industry_sector.manufacturing + t: Manufacturing + - + #tool evaluation + key: options.tool_evaluation.learning_curve_documentation + t: Documentation + - + key: options.tool_evaluation.learning_curve_documentation.description + t: Is it easy to learn and/or well-documented? + - + key: options.tool_evaluation.momentum_popularity + t: Hype & Momentum + - + key: options.tool_evaluation.momentum_popularity.description + t: Is it currently generating a lot of buzz? + - + key: options.tool_evaluation.user_base_size + t: User Base Size + - + key: options.tool_evaluation.user_base_size.description + t: Is it a well-established option with a long track record? + - + key: options.tool_evaluation.developer_experience_tooling + t: Developer Experience + - + key: options.tool_evaluation.developer_experience_tooling.description + t: Does it have good developer tools, a large plugin ecosystem, etc.? + - + key: options.tool_evaluation.performance_user_experience + t: User Experience + - + key: options.tool_evaluation.performance_user_experience.description + t: Does it help you create smooth, performant user experiences? + - + key: options.tool_evaluation.creator_team + t: Creator & Team + - + key: options.tool_evaluation.creator_team.description + t: Is it backed by a well-known, well-funded, or experienced team? + - + key: options.tool_evaluation.accessibility_features + t: Accessibility Features + - + key: options.tool_evaluation.accessibility_features.description + t: Is it good at creating accessible experiences for all users? + - + key: options.tool_evaluation.community_inclusivity + t: Community & Inclusivity + - + key: options.tool_evaluation.community_inclusivity.description + t: Does it have a welcoming, vibrant community built around it? + - + #accessibility features + key: options.accessibility_features.keyboard_navigation + t: Keyboard navigation + - + key: options.accessibility_features.compliant_contrast + t: WCAG-compliant contrast + - + key: options.accessibility_features.focus_indicators + t: Focus indicators + - + key: options.accessibility_features.skip_to_content_link + t: Skip-to-content link + - + key: options.accessibility_features.color_themes + t: Color themes (dark mode, high-contrast mode, etc.) + - + key: options.accessibility_features.prefers_reduced_motion + t: Prefers-reduced-motion + - + key: options.accessibility_features.alt_text + t: Alt texts + - + key: options.accessibility_features.semantic_markup + t: Semantic markup + - + key: options.accessibility_features.aria_attributes + t: ARIA HTML attributes + - + #learning methods + key: options.first_steps.books + t: Books + - + key: options.first_steps.videos + t: Videos & screencasts + - + key: options.first_steps.school + t: School & higher education + - + key: options.first_steps.courses_free + t: Online courses (free) + - + key: options.first_steps.courses_paid + t: Online courses (paid) + - + key: options.first_steps.podcasts + t: Podcasts + - + key: options.first_steps.bootcamp + t: Coding bootcamp + - + key: options.first_steps.on_the_job + t: On-the-job training + - + key: options.first_steps.self_directed + t: Self-directed learning (Google, Stack Overflow, etc.) + - + key: options.first_steps.mentoring + t: Mentoring + - + #degree + key: options.higher_education_degree.no_degree + t: No + - + key: options.higher_education_degree.yes_related + t: Yes, in a field related to my current profession + - + key: options.higher_education_degree.yes_unrelated + t: Yes, but in a field unrelated to my current profession + - + #degree (short versions) + key: options.higher_education_degree.no_degree.short + t: No + - + key: options.higher_education_degree.yes_related.short + t: Yes, related field + - + key: options.higher_education_degree.yes_unrelated.short + t: Yes, unrelated field + - + #bracket + key: options.bracket.round1 + t: Round 1 wins + - + key: options.bracket.round2 + t: Round 2 wins + - + key: options.bracket.round3 + t: Round 3 wins + - + key: options.bracket.combined + t: Combined + - + #email_temporary (receive updates?) + key: options.email_temporary.yes + t: Yes, email me when the survey results are published + - + ########################################################################### + #Tools + ########################################################################### + key: tools.other_tools + t: Other Options + - + key: tools.other_tools.description + t: Other options you use for the current section not mentioned in the list above. + - + key: tools.happiness + t: Overall Happiness + - + key: tools.happiness.description + t: > + On a scale of one (very unhappy) to five (very happy), how happy are you with the current overall state of things as it relates to the options listed above? + - + ########################################################################### + #Demographics (About You/User Info) + ########################################################################### + #age + key: user_info.age + t: Age + - + key: user_info.age.description + t: How old are you, in years? + - + #years of experience + key: user_info.years_of_experience + t: Years of Experience + - + key: user_info.years_of_experience.description + t: How long have you been working or studying in this field, in years? + - + #company size + key: user_info.company_size + t: Company Size + - + key: user_info.company_size.description + t: How big is your company, in number of employees? + - + #salary ranges + key: user_info.yearly_salary + t: Yearly Salary + - + key: user_info.yearly_salary.description + t: Your yearly salary in U.S. dollar. + - + #job title + key: user_info.job_title + t: Job Title + - + key: user_info.job_title.description + t: How do you introduce yourself to others? + - + #javascript proficiency + key: user_info.javascript_proficiency + t: JavaScript Proficiency + - + key: user_info.javascript_proficiency.description + t: How proficient are you at JavaScript? + - + #css proficiency + key: user_info.css_proficiency + t: CSS Proficiency + - + key: user_info.css_proficiency.description + t: How proficient are you at CSS? + - + #backend proficiency + key: user_info.backend_proficiency + t: Back-end Proficiency + - + key: user_info.backend_proficiency.description + t: How proficient are you at back-end development? + - + #gender + key: user_info.gender + t: Gender + - + key: user_info.gender.description + t: > + Which of the following options describes you, if any? Please pick one. + - + key: user_info.gender.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + #race & ethnicity + key: user_info.race_ethnicity + t: Race & Ethnicity + - + key: user_info.race_ethnicity.description + t: > + Which of the following options describe you, if any? Please check all that apply. + - + key: user_info.race_ethnicity.note + t: > + While we know collecting and publishing diversity data can be a sensitive issue, we do think it's important to obtain this data to help measure and improve the survey's efforts in terms of inclusivity and representativeness. + - + key: user_info.race_ethnicity.not_allowed + t: > + In order to comply with local policies, the collection of race or ethnicity data has been disabled for your country or region. + - + #disability status + key: user_info.disability_status + t: Disability Status + - + key: user_info.disability_status.description + t: > + Which of the following disabilities do you experience, if any? Please check all that apply. Note that this can include temporary disabilities or injuries. + - + #disability status (other) + key: user_info.disability_status.others + t: Other Disabilities + - + #other info + key: user_info.how_did_user_find_out_about_the_survey + t: How did you find out about this survey? + - + key: user_info.email + t: Your Email + - + key: user_info.email.description + t: > + You have filled out the survey anonymously. If you'd like, you can optionally enter your email to be able to access your data later on, and be notified when the survey results are published. + - + key: user_info.email.note + t: > + We do not store any personal data, so after you fill in your email address we will use it to generate a unique anonymized identifier and then delete the address itself from our records. + - + key: user_info.country + t: Your Country or Region + - + key: user_info.country.description + t: Where do you currently reside? + - + key: user_info.github_username + t: Your GitHub Username + - + key: user_info.github_username.description + t: > + We might use GitHub usernames in the future to look at repos and cross-reference publicly available information. + - + key: user_info.twitter_username + t: Your Twitter Username + - + key: user_info.twitter_username.description + t: > + We might use Twitter usernames in the future to look at Twitter activity and cross-reference publicly available information (such as the list of people you're following). + - + key: user_info.industry_sector + t: Industry Sector + - + key: user_info.industry_sector.description + t: Which industry sector(s) do you work in? + - + key: user_info.industry_sector.others + t: Other Industry Sectors + - + key: user_info.industry_sector.others.description + t: Other industry sector(s) you work in not mentioned above. + - + #degree + key: user_info.higher_education_degree + t: Higher Education Degree + - + key: user_info.higher_education_degree.description + t: Do you have a higher education degree? + - + #email_temporary (receive updates?) + key: user_info.email_temporary + t: Do you want to be notified when the survey results are released? + - + key: user_info.email_temporary.note + t: > + We don't store any private data, so after your email address is sent to our mailing list provider it will be deleted from our own records. + - + #how can we improve the survey? + key: user_info.how_can_we_improve + t: How could we improve this survey? + - + ########################################################################### + #Other Tools + ########################################################################### + key: tools_others.libraries + t: Libraries + - + key: tools_others.libraries.description + t: Which libraries do you regularly use? + - + key: tools_others.libraries.others + t: Other Libraries + - + key: tools_others.libraries.others.description + t: Other answers (freeform field). + - + key: tools_others.text_editors + t: Text Editors + - + key: tools_others.text_editors.description + t: Which text editor(s) do you regularly use? + - + key: tools_others.text_editors.others + t: Other Text Editors + - + key: tools_others.text_editors.others.description + t: Other answers (freeform field). + - + key: tools_others.utilities + t: Utilities + - + key: tools_others.utilities.description + t: Which utilities or tools do you regularly use? + - + key: tools_others.utilities.others + t: Other Utilities + - + key: tools_others.utilities.others.description + t: Other utilities (freeform field). + - + key: tools_others.browsers + t: Browsers + - + key: tools_others.browsers.description + t: Which browser(s) do you primarily work in during initial development? + - + key: tools_others.browsers.others + t: Other Browsers + - + key: tools_others.browsers.others.description + t: Other answers (freeform field). + - + key: tools_others.build_tools + t: Build Tools + - + key: tools_others.build_tools.description + t: Which build tools do you use? + - + key: tools_others.build_tools.others + t: Other Build Tools + - + key: tools_others.build_tools.others.description + t: Other answers (freeform field). + - + key: tools_others.non_js_languages + t: Non-JavaScript Languages + - + key: tools_others.non_js_languages.description + t: Which other programming languages do you use? + - + key: tools_others.non_js_languages.others + t: Other Languages + - + key: tools_others.non_js_languages.others.description + t: Other answers (freeform field). + - + key: tools_others.javascript_flavors + t: JavaScript Flavors + - + key: tools_others.javascript_flavors.description + t: Languages that compile to JavaScript + - + key: tools_others.javascript_flavors.others + t: Other JavaScript Flavors + - + key: tools_others.javascript_flavors.others.description + t: Other answers (freeform field). + - + ########################################################################### + #Resources + ########################################################################### + #first steps + key: resources.first_steps + t: First Learning Methods + - + key: resources.first_steps.description + t: When first starting out, how did you initially learn coding? + - + key: resources.first_steps.others + t: Other First Learning Methods + - + key: resources.first_steps.others.description + t: Other answers (freeform field). + - + #blogs & magazines + key: resources.blogs_news_magazines + t: Blogs & Magazines + - + key: resources.blogs_news_magazines.description + t: Which blogs/magazines/etc. do you read? + - + key: resources.blogs_news_magazines.others + t: Other Blogs & Magazines + - + key: resources.blogs_news_magazines.others.description + t: Other answers (freeform field). + - + #sites & courses + key: resources.sites_courses + t: Sites & Courses + - + key: resources.sites_courses.description + t: Which sites/courses/etc. do you consult? + - + key: resources.sites_courses.others + t: Other Sites & Courses + - + key: resources.sites_courses.others.description + t: Other answers (freeform field). + - + #podcasts + key: resources.podcasts + t: Podcasts + - + key: resources.podcasts.description + t: Which programming-related podcasts do you listen to? + - + key: resources.podcasts.others + t: Other Podcasts + - + key: resources.podcasts.others.description + t: Other answers (freeform field). + - + #people + key: resources.people + t: People + - + key: resources.people.description + t: People you read, follow, or just want to highlight. + - + #- key: resources.people.others + #t: Other People + #- key: resources.people.others.description + #t: Other answers (freeform field). + key: resources.people.others + t: People + - + key: resources.people.others.description + t: > + People you read, follow, or just want to highlight for their work (freeform field, comma-separated names). + - + #other surveys + key: resources.other_surveys + t: Other Surveys + - + key: resources.other_surveys.description + t: Which other developer surveys do you participate in? + - + key: resources.other_surveys.others + t: Additional surveys not mentioned above